|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [ovmf baseline-only test] 75386: trouble: blocked/broken
This run is configured for baseline tests only. flight 75386 ovmf real [real] http://osstest.xensource.com/osstest/logs/75386/ 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-pvops 4 host-install(4) broken baseline untested build-i386-xsm 4 host-install(4) broken baseline untested build-amd64 4 host-install(4) broken baseline untested build-i386 4 host-install(4) broken baseline untested build-amd64-pvops 4 host-install(4) broken baseline untested build-amd64-xsm 4 host-install(4) broken baseline untested version targeted for testing: ovmf 78af0984b45a780e45d57c22c85a1f594b969212 baseline version: ovmf a7ab1c315c3cf5e804897471e992655c9b5baa0f Last test of basis 75380 2018-10-09 15:20:24 Z 1 days Testing same since 75386 2018-10-10 09:31:54 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Dandan Bi <dandan.bi@xxxxxxxxx> Liming Gao <liming.gao@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-pvops host-install(4) broken-step build-i386-xsm host-install(4) broken-step build-amd64 host-install(4) broken-step build-i386 host-install(4) broken-step build-amd64-pvops host-install(4) broken-step build-amd64-xsm host-install(4) Push not applicable. ------------------------------------------------------------ commit 78af0984b45a780e45d57c22c85a1f594b969212 Author: Dandan Bi <dandan.bi@xxxxxxxxx> Date: Fri Oct 5 16:06:00 2018 +0800 MdePkg: Add PciRoot/PcieRoot text for ACPI Expanded Device Path REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1228 According to UEFI spec,for ACPI Expanded Device Path when HID=PNP0A03 or CID=PNP0A03 and HID != PNP0A08, the device path node can be displayed as: PciRoot(UID|UIDSTR) When HID=PNP0A08 or CID=PNP0A08, the device path node can be displayed as: PcieRoot(UID|UIDSTR). But current code miss the code logic. This commit is to do the enhancement. 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 fb4bea551e5b7e16e54676bca3d1ccde65f57c77 Author: Dandan Bi <dandan.bi@xxxxxxxxx> Date: Fri Oct 5 14:35:25 2018 +0800 MdePkg: Correct condition check for AcpiExp text format REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1226 According to UEFI Spec, for ACPI Expanded Device Path, when HIDSTR=empty, CIDSTR=empty, UID STR!=empty, the ACPI Expanded Device Path node can be displayed as AcpiExp(HID,CID,UIDSTR) format. And if UID is 0 and UIDSTR is empty, then use AcpiEx format. This patch is to correct the condition check to follow UEFI Spec when convert the device path node to the AcpiExp text format. 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 05fe7525896cee197cfed98154955dbaa60d6357 Author: Dandan Bi <dandan.bi@xxxxxxxxx> Date: Fri Oct 5 13:21:57 2018 +0800 MdePkg: Correct the string order of ACPI Expanded Device Path REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1227 According to UEFI Spec, ACPI Expanded Device Path can be display AcpiEx(HID|HIDSTR,(CID|CIDSTR,UID|UIDSTR)), but current code display UID|UIDSTR before CID|CIDSTR. This patch is to fix this issue. 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 959be180e185869b71db9dad34c3f4bba660d724 Author: Dandan Bi <dandan.bi@xxxxxxxxx> Date: Fri Oct 5 09:22:20 2018 +0800 MdePkg: Correct the string expression of UTF8 vendor device path REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1225 According to UEFI spec, the string expression of UTF8 vendor device node should be displayed as: VenUtf8(). Current code display it as: VenUft8() by mistake when convert device path node to text. This commit is to fix this bug. 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 7f8aabef156128976f0c1389c154d25010653215 Author: Dandan Bi <dandan.bi@xxxxxxxxx> Date: Fri Sep 28 13:28:03 2018 +0800 MdeModulePkg/HiiDB: Fix incorrect structure convention for checkbox REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1224 When covert IFR binary to EFI_IFR_CHECKBOX structure, Current code has following incorrect code logic: IfrCheckBox = (EFI_IFR_CHECKBOX *) (IfrOpHdr + 1); The correct one should be: IfrCheckBox = (EFI_IFR_CHECKBOX *) IfrOpHdr; 1. The bug is in function "UpdateDefaultSettingInFormPackage()" which is to update the default setting of some HII Questions in the IFR binary data. So it only has impact when platform overrides default setting in HII VarStore through DynamicHii PCD setting in Platform DSC file. If platform doesn't override default setting, it has no impact. 2. The implementation updates the "Flags" filed in the EFI_IFR_CHECKBOX structure to update the default setting of checkbox. If using "IfrCheckBox = (EFI_IFR_CHECKBOX *) (IfrOpHdr + 1);" when wants to update the " Flags" filed in checkbox, but in fact it will update the opcode binary data(opcode binary length) behind checkbox binary. And then it will cause Browser can't parse the IFR binary data correctly. And then the possible symptom is that some HII Question and forms may be not parsed and then cannot be shown. This patch is to fix this bug. Cc: Liming Gao <liming.gao@xxxxxxxxx> Cc: Star Zeng <star.zeng@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx> Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx> commit 50431b9cc70cd5a084ebd85436bfdd6e2e4b89a7 Author: Liming Gao <liming.gao@xxxxxxxxx> Date: Tue Oct 9 15:06:14 2018 +0800 BaseTools LzmaCompress: Fix GCC warning misleading-indentation GCC 6 or above reports the warning misleading-indentation. This patch fixes it. Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Liming Gao <liming.gao@xxxxxxxxx> Cc: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Acked-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=1234 [lersek@xxxxxxxxxx: reference the BZ that got reported meanwhile] commit 39bbbc87593904a0080d6187ba6863ab565dd985 Author: Liming Gao <liming.gao@xxxxxxxxx> Date: Wed Aug 29 08:51:26 2018 +0800 IntelFrameworkModulePkg Lzma: Update LZMA SDK version to 18.05 https://bugzilla.tianocore.org/show_bug.cgi?id=1006 New formal release in https://www.7-zip.org/sdk.html is 18.05. Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Liming Gao <liming.gao@xxxxxxxxx> Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx> commit f0737de8d9dc591260b1023d4a6a5cd0490ee864 Author: Liming Gao <liming.gao@xxxxxxxxx> Date: Wed Aug 29 08:51:27 2018 +0800 MdeModulePkg Lzma: Update LZMA SDK version to 18.05 https://bugzilla.tianocore.org/show_bug.cgi?id=1006 New formal release in https://www.7-zip.org/sdk.html is 18.05. Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Liming Gao <liming.gao@xxxxxxxxx> Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx> commit 5ec5a236d1fe64b2c40075b6738b74bdf7e1acdc Author: Liming Gao <liming.gao@xxxxxxxxx> Date: Wed Aug 29 08:51:28 2018 +0800 BaseTools Lzma: Update LZMA SDK version to 18.05 https://bugzilla.tianocore.org/show_bug.cgi?id=1006 New formal release in https://www.7-zip.org/sdk.html is 18.05. Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Liming Gao <liming.gao@xxxxxxxxx> Reviewed-by: Star Zeng <star.zeng@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 |