[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [ovmf test] 134935: regressions - FAIL
flight 134935 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/134935/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-ovmf-amd64 21 leak-check/check fail REGR. vs. 134889 test-amd64-i386-xl-qemuu-ovmf-amd64 21 leak-check/check fail REGR. vs. 134889 build-i386-libvirt 6 libvirt-build fail REGR. vs. 134889 version targeted for testing: ovmf d43056888790f987169c54a5c2895758b85dff72 baseline version: ovmf 0eccea3fbe2f6d4999d972d9310d4f2717f5100c Last test of basis 134889 2019-04-16 23:11:24 Z 1 days Testing same since 134935 2019-04-18 01:11:23 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Fan, ZhijuX <zhijux.fan@xxxxxxxxx> Gary Lin <glin@xxxxxxxx> Zhiju.Fan <zhijux.fan@xxxxxxxxx> jobs: build-amd64-xsm pass build-i386-xsm pass build-amd64 pass build-i386 pass build-amd64-libvirt pass build-i386-libvirt fail build-amd64-pvops pass build-i386-pvops pass test-amd64-amd64-xl-qemuu-ovmf-amd64 fail test-amd64-i386-xl-qemuu-ovmf-amd64 fail ------------------------------------------------------------ sg-report-flight on osstest.test-lab.xenproject.org logs: /home/logs/logs images: /home/logs/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Explanation of these reports, and of osstest in general, is at http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ commit d43056888790f987169c54a5c2895758b85dff72 Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Date: Tue Apr 16 13:21:34 2019 -0700 MdeModulePkg/UefiBootManagerLib: fix crash on uninitialized ExitData As reported by Gary, the recent LoadImage/StartImage changes to accommodate dispatching PE/COFF images built for foreign architectures may result in a crash when loading an IA32 option ROM into a X64 VM running OVMF: Loading driver at 0x0007E537000 EntryPoint=0x0007E53C06D 8086100e.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7F003B98 ProtectUefiImageCommon - 0x7F002BC0 - 0x000000007E537000 - 0x000000000009F900 Image type IA32 can't be started on X64 UEFI system. ASSERT MdeModulePkg/Core/Dxe/Mem/Pool.c(698): Head->Signature == ((('p') | ('h' << 8)) | ((('d') | ('0' << 8)) << 16)) || Head->Signature == ((('p') | ('h' << 8)) | ((('d') | ('1' << 8)) << 16)) This turns out to be caused by the deferred image loading code in BDS, which ends up trying to free an uninitialized 'ExitData' pointer. Given that ExitData is never actually used, let's just get rid of it entirely. While we're at it, drop the pointless assignment of Status as well. Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Tested-by: Gary Lin <glin@xxxxxxxx> Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx> Reviewed-by: Hao Wu <hao.a.wu@xxxxxxxxx> commit cfb29d2bda57baa344bded40cf12af81b13e8a40 Author: Fan, ZhijuX <zhijux.fan@xxxxxxxxx> Date: Mon Apr 15 16:55:01 2019 +0800 BaseTools:update ConvertFceToStructurePcd.py with the char order PCD name. BZ:https://bugzilla.tianocore.org/show_bug.cgi?id=1718 BaseTools\Scripts\ConvertFceToStructurePcd.py Update script to sort the PCD order base on PcdName, then base on Pcd field name. Cc: Liming Gao <liming.gao@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Zhiju.Fan <zhijux.fan@xxxxxxxxx> Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx> _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/osstest-output
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |