[Xen-devel] [ovmf baseline-only test] 71374: regressions - FAIL

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

This run is configured for baseline tests only.

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

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-i386-xl-qemuu-ovmf-amd64 15 guest-localmigrate/x10 fail REGR. vs. 
71372

Regressions which are regarded as allowable (not blocking):
 build-amd64-libvirt           5 libvirt-build                fail   like 71372
 build-i386-libvirt            5 libvirt-build                fail   like 71372

version targeted for testing:
 ovmf                 5b78f30d81d7e536df37bafb48c4cb5b6d44edb8
baseline version:
 ovmf                 da0df6ca8f8f118866e53c7fb770598c199993a6

Last test of basis    71372  2017-05-19 19:21:02 Z    0 days
Testing same since    71374  2017-05-20 07:17:30 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Michael D Kinney <michael.d.kinney@xxxxxxxxx>
  Michael Kinney <michael.d.kinney@xxxxxxxxx>

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


------------------------------------------------------------
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 5b78f30d81d7e536df37bafb48c4cb5b6d44edb8
Author: Michael Kinney <michael.d.kinney@xxxxxxxxx>
Date:   Tue May 16 13:35:17 2017 -0700

    UefiCpuPkg/BaseUefiCpuLib: Use NASM read-only data section name
    
    https://bugzilla.tianocore.org/show_bug.cgi?id=556
    
    NASM requires read-only data sections to use the section
    name .rodata.  This fix changes .rdata to .rodata.
    
    The build failure from use of .rdata is seen when using
    the XCODE5 tool chain.
    
    Section "7.8.1 macho extensions to the SECTION Directive"
    of the NASM documentation at http://www.nasm.us/doc/
    describes the section name requirements.
    
    Cc: Jeff Fan <jeff.fan@xxxxxxxxx>
    Cc: Andrew Fish <afish@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Reviewed-by: Jeff Fan <jeff.fan@xxxxxxxxx>

commit 0d0a19cb14ba6867813f56a52cfc89545ad07f3a
Author: Michael Kinney <michael.d.kinney@xxxxxxxxx>
Date:   Thu May 11 15:35:21 2017 -0700

    UefiCpuPkg/PiSmmCpuDxeSmm: Add missing JMP instruction
    
    https://bugzilla.tianocore.org/show_bug.cgi?id=555
    
    Add JMP instruction in SmiEntry.S file that is missing.  This
    updates SmiEntry.S to match the logic in SmiEntry.asm and
    SmiEntry.nasm.
    
    The default BUILDRULEORDER has .nasm higher priority than
    .asm or .S, so this issue was not seen with MSFT or GCC
    tool chain families.  The XCODE5 tool chain overrides the
    BUILDRULEORDER with .S higher than .nasm, so this issue
    was only seen when using XCODE5 tool chain when IA32 SMM
    is enabled.
    
    Cc: Jeff Fan <jeff.fan@xxxxxxxxx>
    Cc: Andrew Fish <afish@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>

commit bbd61de5dbc6ad146dc7250e9646cb662604b5f3
Author: Michael Kinney <michael.d.kinney@xxxxxxxxx>
Date:   Tue May 2 17:23:22 2017 -0700

    PcAtChipsetPkg/SerialIoLib: Remove negative value shift
    
    https://bugzilla.tianocore.org/show_bug.cgi?id=553
    
    Remove left shift of negative values that always evaluate
    to 0 to address build errors from the llvm/clang compiler
    used in the XCODE5 tool chain.
    
    Clang rightfully complains about left-shifting ~DLAB. DLAB is #defined
    as 0x01 (an "int"), hence ~DLAB has value (-2) on all edk2 platforms.
    Left-shifting a negative int is undefined behavior.
    
    Rather than replacing ~DLAB with ~(UINT32)DLAB, realize that the nonzero
    bits of (~(UINT32)DLAB << 7) would all be truncated away in the final
    conversion to UINT8 anyway. So just remove (~DLAB << 7).
    
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Cc: Andrew Fish <afish@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Michael D Kinney <michael.d.kinney@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>

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