[ovmf baseline-only test] 75052: regressions - trouble: blocked/broken/fail/pass

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

This run is configured for baseline tests only.

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

Regressions :-(

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-xsm               5 host-build-prep           fail REGR. vs. 75050
 build-i386                    5 host-build-prep           fail REGR. vs. 75050

Tests which did not succeed, but are not blocking:
 test-amd64-i386-xl-qemuu-ovmf-amd64  1 build-check(1)              blocked n/a
 build-i386-libvirt            1 build-check(1)               blocked  n/a
 test-amd64-amd64-xl-qemuu-ovmf-amd64 10 debian-hvm-install     fail like 75050

version targeted for testing:
 ovmf                 91a5b13650752a54cf766791aa369495c3426485
baseline version:
 ovmf                 d3bc33731f5b039bf3df76e50cbb1f60ce697e9b

Last test of basis    75050  2018-08-06 15:50:05 Z    1 days
Testing same since    75052  2018-08-07 15:19:56 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Brijesh Singh <brijesh.singh@xxxxxxx>
  Laszlo Ersek <lersek@xxxxxxxxxx>

jobs:
 build-amd64-xsm                                              broken  
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   broken  
 build-amd64-libvirt                                          pass    
 build-i386-libvirt                                           blocked 
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         fail    
 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

Push not applicable.

------------------------------------------------------------
commit 91a5b13650752a54cf766791aa369495c3426485
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Fri Aug 3 01:29:13 2018 +0200

    OvmfPkg/PlatformDebugLibIoPort: fix port detection for use in the DXE Core
    
    The DXE Core is one of those modules that call
    ProcessLibraryConstructorList() manually.
    
    Before DxeMain() [MdeModulePkg/Core/Dxe/DxeMain/DxeMain.c] calls
    ProcessLibraryConstructorList(), and through it, our
    PlatformDebugLibIoPortConstructor() function, DxeMain() invokes the
    DEBUG() macro multiple times. That macro lands in our
    PlatformDebugLibIoPortFound() function -- which currently relies on the
    "mDebugIoPortFound" global variable that has (not yet) been set by the
    constructor. As a result, early debug messages from the DXE Core are lost.
    
    Move the device detection into PlatformDebugLibIoPortFound(), also caching
    the fact (not just the result) of the device detection.
    
    (We could introduce a separate DebugLib instance just for the DXE Core,
    but the above approach works for all modules that currently consume the
    PlatformDebugLibIoPort instance (which means "everything but SEC").)
    
    This restores messages such as:
    
    > CoreInitializeMemoryServices:
    >   BaseAddress - 0x7AF21000 Length - 0x3CDE000 MinimalMemorySizeNeeded - 
0x10F4000
    
    Keep the empty constructor function -- OVMF's DebugLib instances have
    always had constructors; we had better not upset constructor dependency
    ordering by making our instance(s) constructor-less.
    
    Cc: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Cc: Brijesh Singh <brijesh.singh@xxxxxxx>
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Fixes: c09d9571300a089c35f5df2773b70edc25050d0d
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Tested-by: Brijesh Singh <brijesh.singh@xxxxxxx>
    [lersek@xxxxxxxxxx: sanitize blank lines around "mDebugIoPortChecked"]

_______________________________________________
osstest-output mailing list
osstest-output@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/osstest-output