[ovmf baseline-only test] 67620: all pass

[Platform Team regression test user <citrix-osstest@xenproject.org>]

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 00afc8f82061677fedc86cb05e3b8c75a3c986ff
baseline version:
 ovmf                 950a3bc788b5b101729b26aed3ff75fd2a64a570

Last test of basis    67619  2016-09-01 09:16:28 Z    0 days
Testing same since    67620  2016-09-01 13:46:26 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Dandan Bi <dandan.bi@intel.com>

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 00afc8f82061677fedc86cb05e3b8c75a3c986ff
Author: Dandan Bi <dandan.bi@intel.com>
Date:   Tue Aug 23 10:29:08 2016 +0800

    ShellPkg: Fix the incorrect return status in function FindFiles()
    
    According to the latest shell spec, in function FindFiles(),
    when no files were found, it should return EFI_NOT_FOUND.
    But current codes don't follow the spec.
    This patch is to fix this issue.
    
    Cc: Ruiyu Ni <ruiyu.ni@intel.com>
    Cc: Jaben Carsey <jaben.carsey@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Dandan Bi <dandan.bi@intel.com>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>

commit c6fc823413861c6bcafbb21bae9aab66b8ee5a24
Author: Dandan Bi <dandan.bi@intel.com>
Date:   Wed Aug 31 13:09:26 2016 +0800

    ShellPkg: Add the check of parameter number in "DrvCfg" command
    
    In shell spec, the usage of "Drvcfg" command is: drvcfg [-l XXX] [-c]
    [-f <Type>|-v|-s] [DriverHandle [DeviceHandle [ChildHandle]]]
    [-i filename] [-o filename]. The parameter number(doesn't include the flags)
    cannot exceed 4, now we add this point to check whether using the command
    correctly.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Dandan Bi <dandan.bi@intel.com>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>
    Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
    Reviewed-by: Tapan Shah <tapandshah@hpe.com>

commit d653d8062e48480a3ec689d688343306bb102b73
Author: Dandan Bi <dandan.bi@intel.com>
Date:   Thu Aug 25 09:37:05 2016 +0800

    ShellPkg: Add check for "dump" parameter in "bcfg" command
    
    When user uses the command "bcfg driver|boot [dump [-v]]",
    the number of command line value parameters (doesn't include the
    flag) must be three. We can add this point to check whether using
    this command correctly.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Dandan Bi <dandan.bi@intel.com>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>
    Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
    Reviewed-by: Tapan Shah <tapandshah@hpe.com>

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