[Xen-devel] [ovmf baseline-only test] 71150: all pass

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

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 83ae7589b08a0d11592527cf45fd1ad8d62118ab
baseline version:
 ovmf                 12b04866af2c348bf7e28e17b4ddc1eaf410211c

Last test of basis    71141  2017-04-01 16:47:07 Z    3 days
Testing same since    71150  2017-04-05 10:47:00 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>

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 83ae7589b08a0d11592527cf45fd1ad8d62118ab
Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
Date:   Tue Apr 4 14:20:12 2017 +0100

    ArmVirtPkg/PlatformPeiLib: honor DT node 'status' property
    
    In some cases, (e.g., when running QEMU with TrustZone emulation), the
    DT may contain DT nodes whose status is set to 'secure'. Similarly, the
    status may be set to 'disabled' if the consumer of the DT image is
    expected to treat it as if it weren't there.
    
    So check whether a 'status' property is present, and if so, ignore the
    node if the status is not 'okay'.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>

commit b1f3e48ed8f9ddd62222953a7b343f9833c71809
Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
Date:   Tue Apr 4 14:07:16 2017 +0100

    ArmVirtPkg/FdtPL011SerialPortLib: honor DT node 'status' property
    
    In some cases, (e.g., when running QEMU with TrustZone emulation), the
    DT may contain DT nodes whose status is set to 'secure'. Similarly, the
    status may be set to 'disabled' if the consumer of the DT image is
    expected to treat it as if it weren't there.
    
    So check whether a 'status' property is present, and if so, ignore the
    node if the status is not 'okay'.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>

commit d014044395b5ac2d37efb65f889dd8910869a332
Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
Date:   Tue Apr 4 13:55:44 2017 +0100

    ArmVirtPkg/FdtClientDxe: honor memory DT node 'status' property
    
    In some cases, (e.g., when running QEMU with TrustZone emulation), the
    DT may contain memory nodes whose status is set to 'secure'. Similarly,
    the status may be set to 'disabled' if the consumer of the DT image is
    expected to treat it as if it weren't there.
    
    So check whether a 'status' property is present, and if so, ignore the
    node if the status is not 'okay'.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>

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