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

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



This run is configured for baseline tests only.

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

Failures :-/ but no regressions.

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

version targeted for testing:
 ovmf                 980af1eb0b7ad7a55fc51231a7fd537529319371
baseline version:
 ovmf                 578dbd52b70061fd3442dc5b050479e4f13b9585

Last test of basis    71602  2017-06-26 15:58:20 Z    1 days
Testing same since    71607  2017-06-27 14:48:15 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Amit Kumar <amit.ak@xxxxxxxxxxx>
  Brijesh Singh <brijesh.singh@xxxxxxx>
  Dandan Bi <dandan.bi@xxxxxxxxx>
  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                                          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 980af1eb0b7ad7a55fc51231a7fd537529319371
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Thu Jun 22 15:22:33 2017 +0800

    ShellPkg DmpStore: Make NameSize to be consistent with name buffer
    
    Current code will allocate pool to hold the null char for name buffer
    when PrevName==NULL, but the NameSize is still 0.
    
    For this case, GetNextVariableName will return EFI_INVALID_PARAMETER
    to follow UEFI 2.7 spec.
    
    UEFI 2.7 spec:
      The VariableNameSize must not be smaller the size of the variable
      name string passed to GetNextVariableName() on input in the
      VariableName buffer.
    
      EFI_INVALID_PARAMETER
      Null-terminator is not found in the first VariableNameSize bytes of
      the input VariableName buffer.
    
    This patch is to make NameSize to be consistent with name buffer.
    
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Cc: Jaben Carsey <jaben.carsey@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>

commit 45b57c1268f42bdad86287b5d41e8c1a86d98834
Author: Dandan Bi <dandan.bi@xxxxxxxxx>
Date:   Mon Jun 26 13:18:20 2017 +0800

    MdeModulePkg/BdsDxe: Report Status Code when booting from BootOrder list
    
    Report Status Code to indicate BDS starts attempting booting
    from the UEFI BootOrder list.
    
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Reviewed-by: Sunny Wang <sunnywang@xxxxxxx>

commit 72259647d0f2eeff65781bc1013674fbd9fd6aa2
Author: Dandan Bi <dandan.bi@xxxxxxxxx>
Date:   Mon Jun 26 11:57:00 2017 +0800

    MdePkg/PiStatusCode: Add new Status Code for BDS when attempting BootOrder
    
    According to new PI spec, add new Status Code to indicate BDS starts
    attempting booting from the UEFI BootOrder list.
    
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Reviewed-by: Sunny Wang <sunnywang@xxxxxxx>

commit fd220166c435479a81dfe8519c92abec9acf7d82
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Tue Jun 27 09:34:13 2017 +0800

    Revert "MdeModulePkg/DxeCore: Fixed Interface returned by CoreOpenProtocol"
    
    This reverts commit 45cfcd8dccf84b8abbc1d6f587fedb5d2037ec79 since it is
    breaking OVMF platform and also real platforms.
    
    REF:
    https://www.mail-archive.com/edk2-devel@xxxxxxxxxxxx/msg26882.html
    https://www.mail-archive.com/edk2-devel@xxxxxxxxxxxx/msg26820.html
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.