[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [ovmf baseline-only test] 68049: all pass



This run is configured for baseline tests only.

flight 68049 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68049/

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 2adf689cb7c66f4790a7d0a9e7e99aad6ebee638
baseline version:
 ovmf                 86a1eca2101686d476ab191f0511b44e369fd8a7

Last test of basis    68046  2016-11-16 03:49:21 Z    0 days
Testing same since    68049  2016-11-16 08:19:13 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Chen A Chen <chen.a.chen@xxxxxxxxx>
  Ruiyu Ni <ruiyu.ni@xxxxxxxxx>

jobs:
 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         pass    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          pass    


------------------------------------------------------------
sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images

Logs, config files, etc. are available at
    http://osstest.xs.citrite.net/~osstest/testlogs/logs

Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary


Push not applicable.

------------------------------------------------------------
commit 2adf689cb7c66f4790a7d0a9e7e99aad6ebee638
Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
Date:   Tue Nov 15 09:57:03 2016 +0800

    ShellPkg: #ifndef of header files should have postfix underscore
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Reviewed-by: Dandan Bi <dandan.bi@xxxxxxxxx>
    Reviewed-by: Jaben Carsey <jaben.carsey@xxxxxxxxx>

commit e9597b4519cbeda1c5175518f79a80d7f0b6353b
Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
Date:   Fri Nov 11 12:12:51 2016 +0800

    ShellPkg/dmpstore: Support "-sfo"
    
    The patch adds the "-sfo" support to "dmpstore" command.
    
    When -l or -d is specified, -sfo is not supported.
    
    When the variable specified by name and GUID cannot be found,
    an error message is displayed; Otherwise, the SFO is displayed.
    E.g.: "dmpstore -guid GuidThatDoesntExist -sfo" produces output
    as:
    ShellCommand,"dmpstore"
    VariableInfo,"","GuidThatDoesntExist","","",""
    
    "dmpstore NameThatDoesntExist -guid GuidThatDoesntExist -sfo"
    produces output as:
    ShellCommand,"dmpstore"
    dmpstore: No matching variables found. Guid GuidThatDoesntExist, Name
    NameThatDoesntExist
    
    The difference between the above 2 cases is that former one only
    specifies the GUID, but the latter one specifies both name and GUID.
    Since not specifying GUID means to use GlobalVariableGuid,
    "dmpstore NameThatDoesntExist -sfo" produces the similar output as
    latter one.
    I personally prefer to always produce SFO output for both cases.
    But the above behavior is the discussion result between HPE engineers.
    
    Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Signed-off-by: Chen A Chen <chen.a.chen@xxxxxxxxx>
    Reviewed-by: Jaben Carsey <jaben.carsey@xxxxxxxxx>
    Reviewed-by: Tapan Shah <tapandshah@xxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.