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

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

This run is configured for baseline tests only.

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

Failures :-/ but no regressions.

Tests which did not succeed, but are not blocking:
 test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install      fail like 75054
 test-amd64-amd64-xl-qemuu-ovmf-amd64 10 debian-hvm-install     fail like 75054

version targeted for testing:
 ovmf                 9e6c4f1527e6f72d6ada10aa39854f2bdd40772f
baseline version:
 ovmf                 b6e48ec6412eab0f21fdff5a045a7ee516574d44

Last test of basis    75054  2018-08-08 12:49:57 Z    0 days
Testing same since    75055  2018-08-08 22:53:08 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Jaben Carsey <jaben.carsey@xxxxxxxxx>
  Liming Gao <liming.gao@xxxxxxxxx>
  Star Zeng <star.zeng@xxxxxxxxx>
  Yunhua Feng <yunhuax.feng@xxxxxxxxx>

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                         fail    
 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.xensource.com/osstest/logs

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


Push not applicable.

------------------------------------------------------------
commit 9e6c4f1527e6f72d6ada10aa39854f2bdd40772f
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Tue Aug 7 18:01:12 2018 +0800

    FmpDevicePkg FmpDxe: Lock variables in entrypoint instead of callback
    
    Current code locks variables in PcdFmpDeviceLockEventGuid callback by
    VariableLock protocol whose interface will be closed at EndOfDxe.
    So the PcdFmpDeviceLockEventGuid callback needs be executed before
    the EndOfDxe callback in Variable driver.
    When PcdFmpDeviceLockEventGuid = gEfiEndOfDxeEventGroupGuid, the
    callback's execution sequence depends on the callback's TPL and
    registration sequence.
    When PcdFmpDeviceLockEventGuid = gEfiEventReadyToBootGuid, the
    PcdFmpDeviceLockEventGuid callback will be executed after the
    EndOfDxe callback in Variable driver, the locking will fail.
    
    The patch moves the variables locking logic to entrypoint.
    The patch also moves the IsLockFmpDeviceAtLockEventGuidRequired ()
    checking to entrypoint.
    
    The entrypoint's final return status should be better to depend on
    the return status of RegisterFmpInstaller/InstallFmpInstance, but not
    gBS->CreateEventEx.
    So the patch also moves the RegisterFmpInstaller/InstallFmpInstance
    calling to the end of entrypoint.
    
    Cc: Michael D Kinney <michael.d.kinney@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Michael D Kinney <michael.d.kinney@xxxxxxxxx>

commit 6ec4d300fe5929a43b9118adc80aa909f61ab665
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Mon Aug 6 15:46:36 2018 +0800

    MdeModulePkg ErstFmpDxe: Create ESRT in ReadyToBoot event
    
    Current code just creates ESRT entry in FMP notification
    and installs ESRT configuration table in ReadyToBoot event.
    
    The LastAttemptVersion and LastAttemptStatus in ESRT will
    be out of date after system continues to boot without reset
    after capsule update (reset is not required or capsule update
    is failed).
    
    This patches updates the code to create ESRT based on all
    FMP instances in ReadyToBoot event.
    
    Cc: Michael D Kinney <michael.d.kinney@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Michael D Kinney <michael.d.kinney@xxxxxxxxx>

commit 27e42bf61bb27a61b5b4dd053c6bc219c73c4cc8
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Mon Aug 6 15:44:59 2018 +0800

    FmpDevicePkg FmpDxe: Need repopulate after SetImage is called
    
    No need repopulate if SetImage is not called.
    But need repopulate after SetImage is called to update
    LastAttemptVersion and LastAttemptStatus
    
    Cc: Michael D Kinney <michael.d.kinney@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Michael D Kinney <michael.d.kinney@xxxxxxxxx>

commit cefc8d8821f0a5ec7995901146dd6b055d7b956a
Author: Yunhua Feng <yunhuax.feng@xxxxxxxxx>
Date:   Mon Aug 6 09:02:25 2018 +0800

    BaseTools: Use gGuidPattern for Guid regular expression
    
    Use GlobalData.py gGuidPattern for Guid regular expression
    
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Yunhua Feng <yunhuax.feng@xxxxxxxxx>
    Reviewed-by: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>

commit 5ac4548cdf6545b08fb04b83b225262d85cb0033
Author: Jaben Carsey <jaben.carsey@xxxxxxxxx>
Date:   Fri Aug 3 07:21:06 2018 +0800

    PatchCheck - add error message for invalid parameter
    
    Currently if an invalid parameter is passed, it gives a stack trace.
    This changes it to an error message.
    
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Jaben Carsey <jaben.carsey@xxxxxxxxx>
    Reviewed-by: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Tested-by: Liming Gao <liming.gao@xxxxxxxxx>

commit e5cbb982562c354a6c040552d0ff20a38202c284
Author: Yunhua Feng <yunhuax.feng@xxxxxxxxx>
Date:   Mon Aug 6 09:08:55 2018 +0800

    BaseTools: Debug message make confused
    
    Debug message make confused
    
    Fix https://bugzilla.tianocore.org/show_bug.cgi?id=995
    
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Yunhua Feng <yunhuax.feng@xxxxxxxxx>
    Reviewed-by: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>

commit 40d1adb3ebf215bacf89d866fd72bfad897daec3
Author: Yunhua Feng <yunhuax.feng@xxxxxxxxx>
Date:   Tue Aug 7 09:35:33 2018 +0800

    BaseTools: Fix incorrect %EDK_TOOLS_PATH%
    
    For non-root folder, such as "X:\test", the EDK_TOOLS_PATH will
    resolve to "X:\test\edk2\BaseTools". This is OK.
    
    But if WORKSPACE is at a root folder, such as "X:\", the EDK_TOOLS_PATH
    will look like "X:\\BaseTools". The *double backslash* can fail the command
    like "del" and thus affect the %ERRORLEVEL% variable, which may break
    subsequent build processing.
    
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Yunhua Feng <yunhuax.feng@xxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

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