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

[ovmf baseline-only test] 75505: trouble: blocked/broken



This run is configured for baseline tests only.

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

Failures and problems with tests :-(

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-pvops               <job status>                 broken
 build-i386-xsm                  <job status>                 broken
 build-amd64                     <job status>                 broken
 build-i386-pvops                <job status>                 broken

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-qemuu-ovmf-amd64  1 build-check(1)             blocked n/a
 build-amd64-libvirt           1 build-check(1)               blocked  n/a
 test-amd64-i386-xl-qemuu-ovmf-amd64  1 build-check(1)              blocked n/a
 build-i386-libvirt            1 build-check(1)               blocked  n/a
 build-i386                    4 host-install(4)       broken baseline untested
 build-i386-pvops              4 host-install(4)       broken baseline untested
 build-amd64                   4 host-install(4)       broken baseline untested
 build-amd64-pvops             4 host-install(4)       broken baseline untested
 build-i386-xsm                4 host-install(4)       broken baseline untested
 build-amd64-xsm               4 host-install(4)       broken baseline untested

version targeted for testing:
 ovmf                 0019375fbc89e4d7cfebe29e288b74731bd9f456
baseline version:
 ovmf                 c637c60273447736b06be971d647cd5e5d2035b8

Last test of basis    75502  2018-10-25 11:50:58 Z    0 days
Testing same since    75505  2018-10-25 19:50:32 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Chasel Chiu <chasel.chiu@xxxxxxxxx>
  Chasel, Chiu <chasel.chiu@xxxxxxxxx>
  Hao Wu <hao.a.wu@xxxxxxxxx>
  Leif Lindholm <leif.lindholm@xxxxxxxxxx>
  Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
  Star Zeng <star.zeng@xxxxxxxxx>
  Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
  Zhiju.Fan <zhijux.fan@xxxxxxxxx>
  zhijufan <zhijux.fan@xxxxxxxxx>

jobs:
 build-amd64-xsm                                              broken  
 build-i386-xsm                                               broken  
 build-amd64                                                  broken  
 build-i386                                                   broken  
 build-amd64-libvirt                                          blocked 
 build-i386-libvirt                                           blocked 
 build-amd64-pvops                                            broken  
 build-i386-pvops                                             broken  
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         blocked 
 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
broken-job build-amd64-pvops broken
broken-job build-i386-xsm broken
broken-job build-amd64 broken
broken-job build-i386-pvops broken
broken-step build-i386 host-install(4)
broken-step build-i386-pvops host-install(4)
broken-step build-amd64 host-install(4)
broken-step build-amd64-pvops host-install(4)
broken-step build-i386-xsm host-install(4)
broken-step build-amd64-xsm host-install(4)

Push not applicable.

------------------------------------------------------------
commit 0019375fbc89e4d7cfebe29e288b74731bd9f456
Author: Leif Lindholm <leif.lindholm@xxxxxxxxxx>
Date:   Tue Oct 2 16:56:08 2018 +0100

    Maintainers.txt: add DynamicTablesPkg
    
    DynamicTablesPkg has been in edk2-staging[1] for some time now, and it is
    time for it to move into the main tree.
    [1] https://github.com/tianocore/edk2-staging/tree/dynamictables
    
    Add Evan and Sami as maintainers of the new package, and let them bring
    it in themselves.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Leif Lindholm <leif.lindholm@xxxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Michael D Kinney <michael.d.kinney@xxxxxxxxx>
    Reviewed-by: Evan Lloyd <evan.lloyd@xxxxxxx>
    Reviewed-by: Sami Mujawar <sami.mujawar@xxxxxxx>

commit b1cc6f672f3b924cdb190e5b92db3b47f46a8911
Author: Chasel, Chiu <chasel.chiu@xxxxxxxxx>
Date:   Fri Oct 19 17:10:30 2018 +0800

    IntelFsp2Pkg: FSP should not override IDT
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1265
    
    FSP should not override IDT table when it is initialized
    by boot loader. IDT should be re-initialized in FSP only
    when it is invalid.
    To mitigate temporary memory usage a PCD
    PcdFspMaxInterruptSupported created for platform to decide
    how many interrupts the FSP IDT table can support.
    
    Test: Verified on internal platform and boots successfully.
    
    Cc: Jiewen Yao <Jiewen.yao@xxxxxxxxx>
    Cc: Desimone Nathaniel L <nathaniel.l.desimone@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Chasel Chiu <chasel.chiu@xxxxxxxxx>
    Reviewed-by: Jiewen Yao <Jiewen.yao@xxxxxxxxx>

commit 5061efe70d020a6811788de2408531f661ef1e45
Author: zhijufan <zhijux.fan@xxxxxxxxx>
Date:   Wed Oct 24 09:08:39 2018 +0800

    BaseTools: list .nasm include inc files as its dependency
    
    .nasm source file may include some header files.
    header file should be listed in Makefile as .nasm source file
    dependency.
    But now, BaseTools doesn't find them and list them in Makefile.
    This is a missing, because original ASM file supports it.
    
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Zhiju.Fan <zhijux.fan@xxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

commit ebed920ffddf1a7de779be3f956415f4160de60d
Author: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
Date:   Tue Oct 23 16:14:28 2018 +0800

    BaseTools: Fix VPD PCD Sub-section display bug
    
    original we get the VPD PCD items from the VPDGuid.map file in the FV
    output folder. but this logic doesn't work when 1) there only have
    single non Default SKU, 2) there have multiple SKU with same value.
    Now we change it to get the really VPD Pcd items that already display
    in the PCD section of the report.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

commit 5d54ab94db0308e90a86aee543cb3a07a9c4d2bc
Author: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
Date:   Wed Oct 24 14:46:09 2018 +0800

    BaseTools: Fix the bug for Pcd used in command line's override
    
    V2: remove the not used parameter i
    
    Fix the bug for Pcd used in command line not override the Pcd used
    in the [component] driver's sub-section.
    
    Case:
    DSC file:
    [PcdsFixedAtBuild]
    TokenSpaceGuid.PcdTest
    
    [Components]
     TestPkg/TestDriver.inf {
      <PcdsFixedAtBuild>
      TokenSpaceGuid.PcdTest|"b"
      }
    
    build command with --pcd TokenSpaceGuid.PcdTest="AAAABB"
    
    Then we found the Pcd value in the AutoGen.c file is incorrect,
    because of the incorrect logic that use the pcd in the [component]
    section to re-override it.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

commit 8411c9d5c4400f9d1d12a6593f5e6b99eb681357
Author: Hao Wu <hao.a.wu@xxxxxxxxx>
Date:   Tue Oct 23 20:57:43 2018 +0800

    MdeModulePkg/NvmExpressDxe: Refine PassThru IO queue creation behavior
    
    REF:https://bugzilla.tianocore.org/show_bug.cgi?id=1260
    
    For the PassThru() service of NVM Express Pass Through Protocol, the
    current implementation (function NvmExpressPassThru()) will only use the
    IO Completion/Submission queues created internally by this driver during
    the controller initialization process. Any other IO queues created will
    not be consumed.
    
    So the value is little to accept external IO Completion/Submission queue
    creation request. This commit will refine the behavior of function
    NvmExpressPassThru(), it will only accept driver internal IO queue
    creation commands and will return "EFI_UNSUPPORTED" for external ones.
    
    Cc: Jiewen Yao <Jiewen.yao@xxxxxxxxx>
    Cc: Star Zeng <star.zeng@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Hao Wu <hao.a.wu@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>

commit 5687ae57232b85d32311d74190031a4dab28c52b
Author: Hao Wu <hao.a.wu@xxxxxxxxx>
Date:   Thu Oct 18 12:52:04 2018 +0800

    MdeModulePkg/NvmExpressDxe: Always copy CQ entry to PassThru packet
    
    REF:https://bugzilla.tianocore.org/show_bug.cgi?id=1259
    
    According to the the NVM Express spec Revision 1.1, for some commands,
    command-related information will be stored in the Dword 0 of the
    completion queue entry.
    
    One case is for the Get Features Command (Section 5.9.2 of the spec),
    Dword 0 of the completion queue entry may contain feature information.
    
    Hence, this commit will always copy the content of completion queue entry
    to the PassThru packet regardless of the execution result of the command.
    
    Cc: Liangcheng Tang <liangcheng.tang@xxxxxxxxx>
    Cc: Star Zeng <star.zeng@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Hao Wu <hao.a.wu@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>

commit ebb6c7633bca47fcd5b460a67e18e4a717ea91cc
Author: Hao Wu <hao.a.wu@xxxxxxxxx>
Date:   Wed Oct 17 10:50:51 2018 +0800

    MdeModulePkg/NvmExpressDxe: Refine data buffer & len check in PassThru
    
    REF:https://bugzilla.tianocore.org/show_bug.cgi?id=1142
    
    According to the the NVM Express spec Revision 1.1, for some commands
    (like Get/Set Feature Command, Figure 89 & 90 of the spec), the Memory
    Buffer maybe optional although the command opcode indicates there is a
    data transfer between host & controller (Get/Set Feature Command, Figure
    38 of the spec).
    
    Hence, this commit refine the checks for the 'TransferLength' and
    'TransferBuffer' field of the EFI_NVM_EXPRESS_PASS_THRU_COMMAND_PACKET
    structure to address this issue.
    
    Cc: Liangcheng Tang <liangcheng.tang@xxxxxxxxx>
    Cc: Star Zeng <star.zeng@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Hao Wu <hao.a.wu@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>

commit 27bf6712b4ea896bf39b00401218ac3b67b683ae
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Wed Oct 24 10:27:48 2018 +0800

    IntelSiliconPkg VTdDxe: Report status code for VTd error
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1273
    
    Current code only uses DEBUG() for VTd error.
    This patch updates to also report status code for VTd error.
    
    Test done:
    Created case that has VTd error and confirmed the error
    status code could be reported as expected.
    
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Cc: Rangasai V Chaganty <rangasai.v.chaganty@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Jiewen Yao <jiewen.yao@xxxxxxxxx>

commit 8c09f300103993985c91532239a72ba879df0b31
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Wed Oct 17 17:43:28 2018 +0800

    IntelSiliconPkg VTdDxe: Option to force no early access attr request
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1272
    
    To have high confidence in usage for platform, add option (BIT2 of
    PcdVTdPolicyPropertyMask) to force no IOMMU access attribute request
    recording before DMAR table is installed.
    
    Check PcdVTdPolicyPropertyMask BIT2 before RequestAccessAttribute()
    and ProcessRequestedAccessAttribute(), then RequestAccessAttribute(),
    ProcessRequestedAccessAttribute() and mAccessRequestXXX variables
    could be optimized by compiler when PcdVTdPolicyPropertyMask BIT2 = 1.
    
    Test done:
    1: Created case that has IOMMU access attribute request before DMAR
       table is installed, ASSERT was triggered after setting
       PcdVTdPolicyPropertyMask BIT2 to 1.
    
    2. Confirmed RequestAccessAttribute(), ProcessRequestedAccessAttribute()
       and mAccessRequestXXX variables were optimized by compiler after
       setting PcdVTdPolicyPropertyMask BIT2 to 1.
    
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Cc: Rangasai V Chaganty <rangasai.v.chaganty@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Jiewen Yao <jiewen.yao@xxxxxxxxx>

commit 0bc7448ad2eafa6f51172c34d24f6a757d5ecf32
Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
Date:   Thu Oct 25 11:19:14 2018 +0800

    MdeModulePkg/UsbBus: Removing trailing spaces
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>

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

 


Rackspace

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