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

[Platform Team regression test user <citrix-osstest@xxxxxxxxxxxxxx>]

This run is configured for baseline tests only.

flight 75347 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75347/

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-amd64-xsm               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-pvops             4 host-install(4)       broken baseline untested
 build-i386-xsm                4 host-install(4)       broken baseline untested

version targeted for testing:
 ovmf                 c0b1f749ef1304810ed4ea58ded65b7f41d79d3e
baseline version:
 ovmf                 c526dcd40f3a0f3a091684481f9c85f03f6a70a7

Last test of basis    75327  2018-09-30 15:52:12 Z    3 days
Testing same since    75347  2018-10-04 00:50:33 Z    0 days    1 attempts

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

jobs:
 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
    http://osstest.xensource.com/osstest/logs

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

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-amd64-xsm host-install(4)
broken-step build-i386-pvops host-install(4)
broken-step build-i386 host-install(4)
broken-step build-amd64-pvops host-install(4)
broken-step build-i386-xsm host-install(4)

Push not applicable.

------------------------------------------------------------
commit c0b1f749ef1304810ed4ea58ded65b7f41d79d3e
Author: Jim.Dailey@xxxxxxxx <Jim.Dailey@xxxxxxxx>
Date:   Wed Oct 3 09:02:24 2018 -0700

    ShellPkg: Create a homefilesystem environment variable
    
    Create a homefilesystem environment variable whose value is the file
    system on which the executing shell is located. For example: "FS14:".
    
    This eliminates the need for people to have to try and find the "boot"
    file system in their startup script.  After this change they can simply
    execute %homefilesystem% to set the cwd to the root of the file system
    where the shell is located.
    
    A future enhancement could be to add "homefilesystem" to the list of
    predefined, read-only variables listed in the EfiShellSetEnv function of
    file ShellProtocol.c
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Jim Dailey <jim_dailey@xxxxxxxx>
    Reviewed-by: Jaben Carsey <jaben.carsey@xxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel