[Xen-devel] [ovmf test] 111080: regressions - FAIL

[osstest service owner <osstest-admin@xxxxxxxxxxxxxx>]

flight 111080 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111080/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail REGR. vs. 
111067
 test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail REGR. vs. 111067

version targeted for testing:
 ovmf                 061ead7a2dcc92c93e97c89fc9892032e7707bda
baseline version:
 ovmf                 578dbd52b70061fd3442dc5b050479e4f13b9585

Last test of basis   111067  2017-06-26 01:46:58 Z    1 days
Testing same since   111076  2017-06-26 15:47:07 Z    0 days    2 attempts

------------------------------------------------------------
People who touched revisions under test:
  Amit Kumar <amit.ak@xxxxxxxxxxx>
  Brijesh Singh <brijesh.singh@xxxxxxx>
  Leo Duran <leo.duran@xxxxxxx>
  Star Zeng <star.zeng@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.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at
    http://logs.test-lab.xenproject.org/osstest/logs

Explanation of these reports, and of osstest in general, is at
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master

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


Not pushing.

------------------------------------------------------------
commit 061ead7a2dcc92c93e97c89fc9892032e7707bda
Author: Leo Duran <leo.duran@xxxxxxx>
Date:   Sat Jun 17 08:41:49 2017 +0800

    UefiCpuPkg: Modify GetProcessorLocationByApicId() to support AMD.
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Cc: Jeff Fan <jeff.fan@xxxxxxxxx>
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Brijesh Singh <brijesh.singh@xxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Leo Duran <leo.duran@xxxxxxx>
    Reviewed-by: Jeff Fan <jeff.fan@xxxxxxxxx>

commit 890d2bd287b5642f4ad59977c5325ac56f4a8203
Author: Leo Duran <leo.duran@xxxxxxx>
Date:   Sat Jun 17 08:41:48 2017 +0800

    UefiCpuPkg: Add CPUID definitions for AMD.
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Cc: Jeff Fan <jeff.fan@xxxxxxxxx>
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Brijesh Singh <brijesh.singh@xxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Leo Duran <leo.duran@xxxxxxx>
    Reviewed-by: Jeff Fan <jeff.fan@xxxxxxxxx>

commit b15cbd9c2d4f240e4268f64ffd6be690b1f0c434
Author: Brijesh Singh <brijesh.singh@xxxxxxx>
Date:   Fri Jun 23 04:37:32 2017 +0800

    UefiCpuPkg: Define AMD Memory Encryption specific CPUID and MSR
    
    The patch defines AMD's Memory Encryption Information CPUID leaf and SEV
    status MSR. The complete description for CPUID leaf is available in APM
    volume 2, Section 15.34.
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Cc: Jeff Fan <jeff.fan@xxxxxxxxx>
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Leo Duran <leo.duran@xxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Brijesh Singh <brijesh.singh@xxxxxxx>
    Reviewed-by: Jeff Fan <jeff.fan@xxxxxxxxx>

commit 4777032247fb3cbc8325881572aa8a83ccd9db93
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Fri Jun 23 17:44:12 2017 +0800

    MdeModulePkg DxeCore: Only free ScratchBuffer when it is not NULL
    
    There is a case that ExtractGuidedSectionGetInfo return 0 for
    ScratchBufferSize and ScratchBuffer will be NULL, after AllocatePool
    fails to allocate buffer for AllocatedOutputBuffer, the code will
    call FreePool (ScratchBuffer), but ScratchBuffer == NULL.
    
    This patch is to only free ScratchBuffer when it is not NULL.
    
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

commit 45cfcd8dccf84b8abbc1d6f587fedb5d2037ec79
Author: Amit Kumar <amit.ak@xxxxxxxxxxx>
Date:   Fri Jun 23 18:09:47 2017 +0800

    MdeModulePkg/DxeCore: Fixed Interface returned by CoreOpenProtocol
    
    Change since v3:
    1) Fixed issue when Attributes = EFI_OPEN_PROTOCOL_TEST_PROTOCOL
    and Inteface = NULL case. [Reported by:star.zeng at intel.com]
    
    Change Since v2:
    1) Modified to use EFI_ERROR to get status code
    
    Change since v1:
    1) Fixed typo protocal to protocol
    2) Fixed coding style
    
    Modified source code to update Interface as per spec.
    1) In case of Protocol is un-supported, interface should be returned NULL.
    2) In case of any error, interface should not be modified.
    3) In case of Test Protocol, interface is optional.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Amit Kumar <amit.ak@xxxxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>

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