|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [ovmf baseline-only test] 75405: trouble: blocked/broken
This run is configured for baseline tests only. flight 75405 ovmf real [real] http://osstest.xensource.com/osstest/logs/75405/ 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-amd64 4 host-install(4) broken baseline untested build-i386-pvops 4 host-install(4) broken baseline untested build-i386 4 host-install(4) broken baseline untested build-amd64-xsm 4 host-install(4) broken baseline untested build-i386-xsm 4 host-install(4) broken baseline untested build-amd64-pvops 4 host-install(4) broken baseline untested version targeted for testing: ovmf bbce001515bbfcad24c216b1c9c25057e8c461e9 baseline version: ovmf 7177be0bd8d372ef7eaa86df538bd45ec841ed23 Last test of basis 75402 2018-10-12 13:20:41 Z 0 days Testing same since 75405 2018-10-12 22:52:25 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Dandan Bi <dandan.bi@xxxxxxxxx> Jeff Brasen <jbrasen@xxxxxxxxxx> Jim Dailey <jim_dailey@xxxxxxxx> Jim.Dailey@xxxxxxxx <Jim.Dailey@xxxxxxxx> 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-amd64 host-install(4) broken-step build-i386-pvops host-install(4) broken-step build-i386 host-install(4) broken-step build-amd64-xsm host-install(4) broken-step build-i386-xsm host-install(4) broken-step build-amd64-pvops host-install(4) Push not applicable. ------------------------------------------------------------ commit bbce001515bbfcad24c216b1c9c25057e8c461e9 Author: Jeff Brasen <jbrasen@xxxxxxxxxx> Date: Wed Oct 10 01:50:37 2018 +0800 MdeModulePkg/SdMmcPciHcDxe: Allow additional SDHCI versions Clock control is similar in SDHCI versions greater then version 2. Add support for more recent versions of the controller specification. SD card support for 1.8V is also present in controller versions 3 and greater. https://bugzilla.tianocore.org/show_bug.cgi?id=1233 Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Jeff Brasen <jbrasen@xxxxxxxxxx> Reviewed-by: Hao Wu <hao.a.wu@xxxxxxxxx> commit bdf038ccff13b2a9d1146598029aa2d6824c4c05 Author: Jeff Brasen <jbrasen@xxxxxxxxxx> Date: Wed Oct 10 01:50:36 2018 +0800 MdeModulePkg/SdMmcPciHcDxe: Add controller version defines Add SDHCI controller defines, this is useful as the version in the register does not explictly map to a specification version. For example vesion 4.10 of the specification is version 0x04. https://bugzilla.tianocore.org/show_bug.cgi?id=1233 Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Jeff Brasen <jbrasen@xxxxxxxxxx> Reviewed-by: Hao Wu <hao.a.wu@xxxxxxxxx> commit 9343d0a1cd09544686b14dba5b428d7bc811f6b9 Author: Dandan Bi <dandan.bi@xxxxxxxxx> Date: Fri Oct 5 17:30:31 2018 +0800 MdePkg: Use VENDOR_DEVICE_PATH structure for Debug Port device path REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1229 When converting DebugPort device path from text, current code use VENDOR_DEFINED_MESSAGING_DEVICE_PATH structure for Debug port device node. typedef struct { EFI_DEVICE_PATH_PROTOCOL Header; EFI_GUID Guid; UINT8 VendorDefinedData[1]; } VENDOR_DEFINED_MESSAGING_DEVICE_PATH; And Debugport Device Path is a vendor-defined messaging device path with no data, only a GUID. So it's better to use VENDOR_DEVICE_PATH to create the Debug port device node. typedef struct { EFI_DEVICE_PATH_PROTOCOL Header; EFI_GUID Guid; } VENDOR_DEVICE_PATH; Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Cc: Michael D Kinney <michael.d.kinney@xxxxxxxxx> Cc: Liming Gao <liming.gao@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx> Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> commit b1df6c258249ae6cfaa5d0665a9cad99d9f22675 Author: Jim.Dailey@xxxxxxxx <Jim.Dailey@xxxxxxxx> Date: Fri Oct 5 00:46:39 2018 +0800 ShellPkg-Cd: Ensure all valid cd targets are handled properly ShellPkg-Cd: Ensure all valid cd targets are handled properly Make sure that PathCleanUpDirectories() is called on all valid targets of the cd command. Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Jim Dailey <jim_dailey@xxxxxxxx> Reviewed-by: Jaben Carsey <jaben.carsey@xxxxxxxxx> Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |