flight 188281 ovmf real [real] flight 188285 ovmf real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/188281/ http://logs.test-lab.xenproject.org/osstest/logs/188285/
Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 188152 version targeted for testing: ovmf 8f84eb0e761992dc1218f63ee53a54ac0c65630f baseline version: ovmf e19cc32bce466fb1c175f7d44708c2ebb45802a7 Last test of basis 188152 2024-10-17 07:11:33 Z 1 days Failing since 188156 2024-10-17 09:14:11 Z 1 days 11 attempts Testing same since 188268 2024-10-18 18:13:31 Z 0 days 3 attempts ------------------------------------------------------------ People who touched revisions under test: jack Hsieh <[email protected]> Jeremy Compostella <[email protected]> Kun Qin <[email protected]> Kun Qin <[email protected]> Mike Beaton <[email protected]> Sienski Piotr <[email protected]> v-chhsieh <[email protected]> jobs: build-amd64-xsm pass build-i386-xsm pass build-amd64 pass build-i386 pass build-amd64-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-i386-pvops pass test-amd64-amd64-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 8f84eb0e761992dc1218f63ee53a54ac0c65630f Author: Mike Beaton <[email protected]> Date: Sun Sep 29 11:40:44 2024 +0100 BaseTools: Remove -Wno-unneeded-internal-declaration from CLANGDWARF Subsequent to updating the 'null' DEBUG macro to explicitly discard its expression, it is possible to remove this warning suppression from CLANGDWARF and still successfully compile its RELEASE build. Note that CLANGPDB did and does not have this warning suppressed, and so before updating the 'null' DEBUG macro, CLANGPDB RELEASE was not building successfully in recent versions of clang, but was stopping with the error: .../edk2/OvmfPkg/VirtioSerialDxe/VirtioSerial.c:28:22: error: variable 'EventNames' is not needed and will not be emitted [-Werror,-Wunneeded-internal-declaration] STATIC CONST CHAR8 *EventNames[] = { ^ This change makes the two CLANG variants match with respect to this warning, and leaves the warning enabled which is considered a benefit as it has the potential to catch real coding errors Signed-off-by: Mike Beaton <[email protected]> commit ae83c6b7fd83a5906e016a32027c1bcd792a624e Author: Mike Beaton <[email protected]> Date: Sat Sep 28 02:43:15 2024 +0100 MdePkg: Fix null macros for XCODE5 and CLANG When building OvmfPkg in RELEASE mode in the XCODE5 toolchain, the ASSERT_EFI_ERROR change prevents this error: .../MdePkg/Library/UefiMemoryAllocationLib/MemoryAllocationLib.c:141:15: error: variable 'Status' set but not used [-Werror,-Wunused-but-set-variable] EFI_STATUS Status; ^ which is currently stopping the build. When building in RELEASE mode in the CLANGPDB toolchain,the DEBUG macro change prevents this error: .../edk2/OvmfPkg/VirtioSerialDxe/VirtioSerial.c:28:22: error: variable 'EventNames' is not needed and will not be emitted [-Werror,-Wunneeded-internal-declaration] STATIC CONST CHAR8 *EventNames[] = { ^ which is currently stopping the build. CLANGDWARF produces the same error as CLANGPDB above, if -Wno-unneeded-internal-declaration is removed from its build flags. With the null DEBUG macro change, this warning suppression can be removed from CLANGDWARF, which is considered a benefit as it has the potential to catch real coding errors. This is done in a subsequent commit. This commit has the desirable side effect that we no longer require (and cannot use) explicit `#ifndef MDEPKG_NDEBUG` around items only used in DEBUG macros. This requires the ArmPkg change made here to be in the same commit as the MdePkg changes. Note: In common with existing macros in EDK II, including the pre-existing and unchanged DEBUG/NOOPT versions of the macros which are modified here, we use the standard approach of adding `do { ... } while (FALSE)` wrapping to ensure that the macros behave correctly with surrounding code (e.g. require a following ';' and do not combine in unexpected ways with nearby conditionals). Continuous-integration-options: PatchCheck.ignore-multi-package Co-authored-by: Mikhail Krichanov <[email protected]> Signed-off-by: Mike Beaton <[email protected]> commit 6e197a8ba5e349e511850fc52457992de88c8795 Author: v-chhsieh <[email protected]> Date: Mon Sep 30 14:43:39 2024 +0800 MdePkg: Add Google Test Library and Protocol Mock Libraries: MdePkg\Test\Mock\Library\GoogleTest\MockCpuLib MdePkg\Test\Mock\Library\GoogleTest\MockPciSegmentLib MdePkg\Test\Mock\Library\GoogleTest\MockReportStatusCodeLib MdePkg\Test\Mock\Library\GoogleTest\MockSmmServicesTableLib Mock Protocol: MdePkg\Test\Mock\Include\GoogleTest\Protocol\MockMpService.h Signed-off-by: jack Hsieh <[email protected]> Cc: Maintainer Shruti Gupta <[email protected]> Cc: Reviewer Shruti Gupta <[email protected]> commit 866abb233817eb349fa5fe2b32283e990a8e5056 Author: Jeremy Compostella <[email protected]> Date: Wed Oct 9 15:03:13 2024 -0700 MdeModulePkg: Replace right bit shift operator with RShiftU64 Instead of using bit shift operations, it is preferable to use BaseLib bit shift functions to prevent compilers from inserting intrinsics. Signed-off-by: Jeremy Compostella <[email protected]> commit 996e740cc83aa499d91b3ab3ae857dab7578e05c Author: Jeremy Compostella <[email protected]> Date: Tue Oct 8 16:55:51 2024 -0700 MdeModulePkg: Fix PeiAllocatePages() corner case I recently ran into an AllocatePages() hang. It turns out that AllocatePages() does not account for the Memory Allocation HOB when it makes the decision of allocating out of free memory. Here is the scenario: FreeMemoryTop - 0x71C03000 FreeMemoryBottom - 0x71BDBFD8 => We have 159,784 bytes left => ~39.0098 pages left. We attempt to allocate 39 pages. There are enough pages left but allocating those pages requires to allocate a Memory Allocation HOB which needs an extra 48 bytes. But once the pages are allocated, there are only 40 bytes left. In addition to taking into account the Memory Allocation HOB size, this commit reverses the condition to keep it simple. Signed-off-by: Jeremy Compostella <[email protected]> commit 1b70dcd375765d293f57fe546710b98525e6a46d Author: Sienski Piotr <[email protected]> Date: Mon Oct 14 12:24:14 2024 +0200 MdePkg/Include/Guid: Add missing CXL definitions to Cper.h [Issue Description] In MdePkg/Include/Guid/Cper.h there are missing multiple definitions regarding CXL that can be found in UEFI 2.10 spec chapters N.2.13 and N.2.14 [Resolution] Add these definitions to MdePkg/Include/Guid/Cper.h Signed-off-by: Sienski Piotr <[email protected]> commit 79598f34fa024ad2491b46b95c3189c5a7f159d2 Author: Kun Qin <[email protected]> Date: Wed Aug 10 22:56:34 2022 -0700 MdeModulePkg: PeiMain: Updated dispatcher for delayed dispatch REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4496 This change adds a check for PEI dispatcher to continue dispatching when there are still pending delayed dispatch requests, to be compatible with newly integrated Delayed Dispatcher PPI interface. Cc: Jian J Wang <[email protected]> Cc: Liming Gao <[email protected]> Cc: Dandan Bi <[email protected]> Cc: Debkumar De <[email protected]> Cc: Catharine West <[email protected]> Co-authored-by: John Schock <[email protected]> Signed-off-by: Kun Qin <[email protected]> commit d64d1e195ceb003c824786bfd817227c7ae81f06 Author: Kun Qin <[email protected]> Date: Thu Sep 19 14:11:37 2024 -0700 MdeModulePkg: PeiMain: Introduce implementation of delayed dispatch REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4496 This change adds the implementation that fits the needs and description of PI spec defined Delayed Dispatch PPI in Pei Core. The PPI would allow minimal delay for registered callbacks. As well as allowing other functions to wait for GUIDed delayed dispatch callbacks. Cc: Jian J Wang <[email protected]> Cc: Dandan Bi <[email protected]> Cc: Liming Gao <[email protected]> Cc: Debkumar De <[email protected]> Cc: Catharine West <[email protected]> Co-authored-by: Mike Turner <[email protected]> Co-authored-by: Sachin Ganesh <[email protected]> Signed-off-by: Kun Qin <[email protected]> commit b3f36e151d8b014cac5c6a833e2270c14d998739 Author: Kun Qin <[email protected]> Date: Thu Sep 19 14:09:03 2024 -0700 MdePkg: Update Delayed Dispatch PPI as per PI 1.8 A Spec REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4496 PI spec defined the `Register` function input argument `Delay` as output. However, this parameter should be used to define the minmal time delay the callback should fire. Thus it should be an input parameter. This change fixed the argument type. Cc: Michael D Kinney <[email protected]> Cc: Liming Gao <[email protected]> Cc: Zhiguang Liu <[email protected]> Co-authored-by: Mike Turner <[email protected]> Co-authored-by: Sachin Ganesh <[email protected]> Signed-off-by: Kun Qin <[email protected]>
