|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [ovmf baseline-only test] 75496: trouble: blocked/broken
This run is configured for baseline tests only. flight 75496 ovmf real [real] http://osstest.xensource.com/osstest/logs/75496/ 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-i386-xsm 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 a8b5750901faa63ff5570634851e648b8e335e5a baseline version: ovmf a58a421c3629e5f28b4a6887c28da4ee6976cd61 Last test of basis 75493 2018-10-24 07:50:43 Z 0 days Testing same since 75496 2018-10-24 18:51:46 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Dandan Bi <dandan.bi@xxxxxxxxx> Herbie Robinson <Herbie.Robinson@xxxxxxxxxxx> Jim Dailey <jim_dailey@xxxxxxxx> Jim.Dailey@xxxxxxxx <Jim.Dailey@xxxxxxxx> Robinson, Herbie <Herbie.Robinson@xxxxxxxxxxx> Ruiyu Ni <ruiyu.ni@xxxxxxxxx> shenglei <shenglei.zhang@xxxxxxxxx> Shenglei Zhang <shenglei.zhang@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-i386-xsm host-install(4) broken-step build-amd64-pvops host-install(4) broken-step build-amd64-xsm host-install(4) Push not applicable. ------------------------------------------------------------ commit a8b5750901faa63ff5570634851e648b8e335e5a Author: Dandan Bi <dandan.bi@xxxxxxxxx> Date: Fri Oct 12 10:18:28 2018 +0800 MdePkg: Handle AcpiExp device path when optional para is not specified REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1243 AcpiExp text device path: AcpiExp(HID,CID,UIDSTR) And according to UEFI spec, the CID parameter is optional and has a default value of 0. But current implementation miss to check following cases for the AcpiExp. FromText:when text device is AcpiExp(HID,,UIDSTR)/AcpiExp(HID,0,UIDSTR) ToText: when the CID is 0 in the node structure 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.1 Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx> Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> commit 3874108034eb3f1d5d5180df33a5dfdd5fab5d25 Author: Dandan Bi <dandan.bi@xxxxxxxxx> Date: Fri Oct 12 10:18:27 2018 +0800 MdePkg: Handle USBxxx device path when optional para is not specified REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1243 According to UEFI spec, for the Messaging Device Path with USB Class SubType, some paras are optional in the text device path. Take UsbClass(VID,PID,Class,SubClass,Protocol) for example, The VID is an integer between 0 and 65535 and is optional. The default value is 0xFFFF. The PID is an integer between 0 and 65535 and is optional. The default value is 0xFFFF. The Class is an integer between 0 and 255 and is optional. The default value is 0xFF. The SubClass is an integer between 0 and 255 and is optional. The default value is 0xFF. The Protocol is an integer between 0 and 255 and is optional. The default value is 0xFF. So if any the optional para is not specified in the text device, we should set related para in the node structure to default value. This commit is to do the enhancement for USB Class device path when optional para is not specified 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.1 Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx> Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> commit 6d9b9bbb6148831de2ca545994f31e27b3d4c675 Author: Dandan Bi <dandan.bi@xxxxxxxxx> Date: Fri Oct 12 10:18:26 2018 +0800 MdePkg: Handle Sata device path when optional para is not specified REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1243 Sata device path format:Sata(HPN, PMPN, LUN) According to UEFI Spec, the PMPN is an integer between 0 and 65535 and is optional. If not provided, the default is 0xFFFF. This commit is to do the enhancement for Sata device path when optional para is not specified. 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.1 Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx> Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> commit ea1486c28127057b7f3059b8c3c74afe7912460f Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Date: Wed Oct 24 15:22:31 2018 +0800 FatPkg: Correct the line ending to CRLF Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> commit b08b045ca9ab46f335d2edc21eeea5340a1aea6b Author: Jim.Dailey@xxxxxxxx <Jim.Dailey@xxxxxxxx> Date: Sat Oct 6 03:14:56 2018 +0800 MdePkg-BaseLib: Fix PathCleanUpDirectories() issue with "\\..\\.." Replace multiple, consecutive "\" characters prior to other processing involving "\" characters. This fixes an issue where "\\..\\..", "//..//..", and similar input paths are not cleaned properly. Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Jim Dailey <jim_dailey@xxxxxxxx> Reviewed-by: Ruiyu Ni <Ruiyu.ni@xxxxxxxxx> Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx> commit add1310df55eede2f52f44a021802831c683577d Author: Robinson, Herbie <Herbie.Robinson@xxxxxxxxxxx> Date: Fri Sep 7 08:07:09 2018 +0800 FatPkg/EnhancedFatDxe Fix Double Cluster Allocation This is a fix for a double cluster allocation when the disk is full. The double allocation happens because FatGrowEof calls FatAllocateCluster without immediately marking the each returned cluster as allocated. The fix is to move the FatSetFatEntry call inside the loop. I've also include some improvements to the sanity checks that I added while tracking this down. They are optional. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Herbie Robinson <Herbie.Robinson@xxxxxxxxxxx> Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> commit 8a2794f6f3a42bcc878a30565e1db9ac96fdc7cd Author: shenglei <shenglei.zhang@xxxxxxxxx> Date: Tue Oct 16 13:55:51 2018 +0800 FatBinPkg: Remove FatBinPkg and refresh document Remove FatBinPkg and refresh Maintainers.txt. https://bugzilla.tianocore.org/show_bug.cgi?id=1105 Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Shenglei Zhang <shenglei.zhang@xxxxxxxxx> Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx> Reviewed-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Reviewed-by: Andrew Fish <afish@xxxxxxxxx> Reviewed-by: Leif Lindholm <leif.lindholm@xxxxxxxxxx> commit f1a7d73a6880471b2f006044995276f65f44428a Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Date: Thu Oct 11 15:51:45 2018 +0800 ShellPkg/dmem: Only dump sizeof (EFI_SYSTEM_TABLE) bytes for gST REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1236 When "dmem" runs without additional arguments, it dumps the memory content of EFI_SYSTEM_TABLE. But today's implementation dumps 512 bytes. It's not correct because sizeof (EFI_SYSTEM_TABLE) is less than 512, the 512-read causes page fault exception in a heap-guard enabled environment. The patch changes the implementation to only dump sizeof (EFI_SYSTEM_TABLE) bytes for gST. Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Cc: Jaben Carsey <jaben.carsey@xxxxxxxxx> Reviewed-by: Jim Dailey <jim_dailey@.com> _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/osstest-output
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |