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

[Xen-devel] [ovmf baseline-only test] 71456: tolerable FAIL



This run is configured for baseline tests only.

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

Failures :-/ but no regressions.

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

version targeted for testing:
 ovmf                 b9036ebee9ddaf26afc9fbe3236c3d03f83c1b0a
baseline version:
 ovmf                 f4d3ba87bb8f5d82d3b80532ea4c83b7bbca41c0

Last test of basis    71453  2017-05-28 14:49:57 Z    1 days
Testing same since    71456  2017-05-29 20:19:57 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Laszlo Ersek <lersek@xxxxxxxxxx>

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                          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 b9036ebee9ddaf26afc9fbe3236c3d03f83c1b0a
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Thu May 18 14:48:13 2017 +0200

    QuarkPlatformPkg/SpiFvbServices: correct NumOfLba vararg type in 
EraseBlocks()
    
    According to the PI spec, Volume 3,
    EFI_FIRMWARE_VOLUME_BLOCK2_PROTOCOL.EraseBlocks():
    
    > The variable argument list is a list of tuples. Each tuple describes a
    > range of LBAs to erase and consists of the following:
    > * An EFI_LBA that indicates the starting LBA
    > * A UINTN that indicates the number of blocks to erase
    
    (NB, in edk2, EFI_FIRMWARE_VOLUME_BLOCK_PROTOCOL is a typedef to
    EFI_FIRMWARE_VOLUME_BLOCK2_PROTOCOL.)
    
    In this driver, the NumOfLba local variable is defined with type UINTN,
    but the TYPE argument passed to VA_ARG() is UINT32. Fix the mismatch.
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Cc: Kelly Steele <kelly.steele@xxxxxxxxx>
    Cc: Michael D Kinney <michael.d.kinney@xxxxxxxxx>
    Reported-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Reviewed-by: Michael D Kinney <michael.d.kinney@xxxxxxxxx>

commit d0d7289cce487eabc2180bb5b065886a37a257bd
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Thu May 18 14:48:13 2017 +0200

    Nt32Pkg/FvbServicesRuntimeDxe: correct NumOfLba vararg type in EraseBlocks()
    
    According to the PI spec, Volume 3,
    EFI_FIRMWARE_VOLUME_BLOCK2_PROTOCOL.EraseBlocks():
    
    > The variable argument list is a list of tuples. Each tuple describes a
    > range of LBAs to erase and consists of the following:
    > * An EFI_LBA that indicates the starting LBA
    > * A UINTN that indicates the number of blocks to erase
    
    (NB, in edk2, EFI_FIRMWARE_VOLUME_BLOCK_PROTOCOL is a typedef to
    EFI_FIRMWARE_VOLUME_BLOCK2_PROTOCOL.)
    
    In this driver, the NumOfLba local variable is defined with type UINTN,
    but the TYPE argument passed to VA_ARG() is UINT32. Fix the mismatch.
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Reported-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Reviewed-by: Hao Wu <hao.a.wu@xxxxxxxxx>

commit d98e939f4fd72d3f426e0005beba554de5fb9bd0
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Thu May 18 14:48:13 2017 +0200

    DuetPkg/FvbRuntimeService: correct NumOfLba vararg type in EraseBlocks()
    
    According to the PI spec, Volume 3,
    EFI_FIRMWARE_VOLUME_BLOCK2_PROTOCOL.EraseBlocks():
    
    > The variable argument list is a list of tuples. Each tuple describes a
    > range of LBAs to erase and consists of the following:
    > * An EFI_LBA that indicates the starting LBA
    > * A UINTN that indicates the number of blocks to erase
    
    (NB, in edk2, EFI_FIRMWARE_VOLUME_BLOCK_PROTOCOL is a typedef to
    EFI_FIRMWARE_VOLUME_BLOCK2_PROTOCOL.)
    
    In this driver, the NumOfLba local variable is defined with type UINTN,
    but the TYPE argument passed to VA_ARG() is UINT32. Fix the mismatch.
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Reported-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Reviewed-by: Hao Wu <hao.a.wu@xxxxxxxxx>

_______________________________________________
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®.