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

[Xen-devel] [ovmf baseline-only test] 75402: trouble: blocked/broken

This run is configured for baseline tests only.

flight 75402 ovmf real [real]

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64-xsm                 <job status>                 broken
 build-i386                      <job status>                 broken
 build-amd64-pvops               <job status>                 broken
 build-i386-xsm                  <job status>                 broken
 build-amd64                     <job status>                 broken
 build-i386-pvops                <job status>                 broken

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-qemuu-ovmf-amd64  1 build-check(1)             blocked n/a
 build-amd64-libvirt           1 build-check(1)               blocked  n/a
 test-amd64-i386-xl-qemuu-ovmf-amd64  1 build-check(1)              blocked n/a
 build-i386-libvirt            1 build-check(1)               blocked  n/a
 build-amd64                   4 host-install(4)       broken baseline untested
 build-i386-pvops              4 host-install(4)       broken baseline untested
 build-i386                    4 host-install(4)       broken baseline untested
 build-amd64-xsm               4 host-install(4)       broken baseline untested
 build-i386-xsm                4 host-install(4)       broken baseline untested
 build-amd64-pvops             4 host-install(4)       broken baseline untested

version targeted for testing:
 ovmf                 7177be0bd8d372ef7eaa86df538bd45ec841ed23
baseline version:
 ovmf                 8122c6bc8b6f1fde31f2af6c1560ec552204980d

Last test of basis    75398  2018-10-12 00:20:37 Z    0 days
Testing same since    75402  2018-10-12 13:20:41 Z    0 days    1 attempts

People who touched revisions under test:
  Jim Dailey <jim_dailey@xxxxxxxx>
  Jim.Dailey@xxxxxxxx <Jim.Dailey@xxxxxxxx>

 build-amd64-xsm                                              broken  
 build-i386-xsm                                               broken  
 build-amd64                                                  broken  
 build-i386                                                   broken  
 build-amd64-libvirt                                          blocked 
 build-i386-libvirt                                           blocked 
 build-amd64-pvops                                            broken  
 build-i386-pvops                                             broken  
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         blocked 
 test-amd64-i386-xl-qemuu-ovmf-amd64                          blocked 

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

Logs, config files, etc. are available at

Test harness code can be found at

broken-job build-amd64-xsm broken
broken-job build-i386 broken
broken-job build-amd64-pvops broken
broken-job build-i386-xsm broken
broken-job build-amd64 broken
broken-job build-i386-pvops broken
broken-step build-amd64 host-install(4)
broken-step build-i386-pvops host-install(4)
broken-step build-i386 host-install(4)
broken-step build-amd64-xsm host-install(4)
broken-step build-i386-xsm host-install(4)
broken-step build-amd64-pvops host-install(4)

Push not applicable.

commit 7177be0bd8d372ef7eaa86df538bd45ec841ed23
Author: Jim.Dailey@xxxxxxxx <Jim.Dailey@xxxxxxxx>
Date:   Thu Oct 4 23:03:28 2018 +0800

    MdePkg-BaseLib: Fix PathCleanUpDirectories() error involving "\..\.."
    MdePkg-BaseLib: Fix PathCleanUpDirectories() error involving "\..\.."
    The loop that removes "xxxx\..\" errs when multiple "\.." sequences are
    in the path.  Before this change the code would modify a path like
    "FS0:\efi\tools\..\.." to "FS0:\efi\\.." and then to "FS0:\efi\", but
    the correct path is "FS0:\".
    You can test the effect of this change in the shell by setting the
    current directory to something like FS0:\efi\boot and then executing
    the command "ls ..\..".  Before the change you will see the files in
    the FS0:\efi directory; after the change, you will see the files in
    the root directory of FS0:.
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Jim Dailey <jim_dailey@xxxxxxxx>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>

Xen-devel mailing list



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