Re: [PULL 00/10] PPC PR for 11.0 soft-freeze
On 11/03/26 13:23, Thomas Huth wrote: On 11/03/2026 07.03, Aditya Gupta wrote: Hello Peter, I run the pipeline everytime before sending, curious about the tests I missed. 1. How can I get the console log of the failed centos test ? Or how to (or if I can) run that test on my system ? I did not find the log in the gitlab test's artifacts. Surprised with the failure on the particular centos distro. The console log can be found here: https://gitlab.com/qemu-project/qemu/-/jobs/13431423958/artifacts/browse/build/tests/functional/ppc64/test_fadump.QEMUFadump.test_fadump_powernv/ See docs/devel/testing/functional.rst for information on how to run functional tests locally. 2. Is there a way to enable these tests, or to get access to these tests: aarch64-macos-build & x64-freebsd-14-build I read these are run using cirrus ci, can these be run on our systems, if not on gitlab ? See .gitlab-ci.d/cirrus/README.rst for information on how to set up the Cirrus-CI for your own cloned repository on gitlab. Thank you Thomas ! Will read it. Thanks, - Aditya G HTH, Thomas
Re: [PULL 00/10] PPC PR for 11.0 soft-freeze
On 11/03/2026 07.03, Aditya Gupta wrote: Hello Peter, I run the pipeline everytime before sending, curious about the tests I missed. 1. How can I get the console log of the failed centos test ? Or how to (or if I can) run that test on my system ? I did not find the log in the gitlab test's artifacts. Surprised with the failure on the particular centos distro. The console log can be found here: https://gitlab.com/qemu-project/qemu/-/jobs/13431423958/artifacts/browse/build/tests/functional/ppc64/test_fadump.QEMUFadump.test_fadump_powernv/ See docs/devel/testing/functional.rst for information on how to run functional tests locally. 2. Is there a way to enable these tests, or to get access to these tests: aarch64-macos-build & x64-freebsd-14-build I read these are run using cirrus ci, can these be run on our systems, if not on gitlab ? See .gitlab-ci.d/cirrus/README.rst for information on how to set up the Cirrus-CI for your own cloned repository on gitlab. HTH, Thomas
Re: [PULL 00/10] PPC PR for 11.0 soft-freeze
Hello Peter, I run the pipeline everytime before sending, curious about the tests I missed. 1. How can I get the console log of the failed centos test ? Or how to (or if I can) run that test on my system ? I did not find the log in the gitlab test's artifacts. Surprised with the failure on the particular centos distro. 2. Is there a way to enable these tests, or to get access to these tests: aarch64-macos-build & x64-freebsd-14-build I read these are run using cirrus ci, can these be run on our systems, if not on gitlab ? Thanks for the suggestions Peter, i have the fixes ready for the next version. Thanks, - Aditya G
Re: [PULL 00/10] PPC PR for 11.0 soft-freeze
On Tue, 10 Mar 2026 at 16:14, Harsh Prateek Bora wrote: > > + Aditya > > Hi Peter, > > Is there a way to trigger aarch64-macos-build and x64-freebsd-14-build > from Qemu gitlab CI? I had run the CI pipeline with below job and I do > not see those tests getting listed/executed: > > https://gitlab.com/harshpb/qemu/-/pipelines/2375854439 Yeah, some of the CI jobs are not run under user pipelines because they use external/project resources. I think the macos and freebsd ones run via Cirrus. -- PMM
Re: [PULL 00/10] PPC PR for 11.0 soft-freeze
+ Aditya Hi Peter, Is there a way to trigger aarch64-macos-build and x64-freebsd-14-build from Qemu gitlab CI? I had run the CI pipeline with below job and I do not see those tests getting listed/executed: https://gitlab.com/harshpb/qemu/-/pipelines/2375854439 Aditya, Could you please take a look at below listed CI failures and address it? Thanks Harsh On 10/03/26 9:23 pm, Peter Maydell wrote: On Tue, 10 Mar 2026 at 15:15, Harsh Prateek Bora wrote: The following changes since commit ae56950eac7b61b1abf42003329ee0f3ce111711: Merge tag 'firmware-20260310-pull-request' of https://gitlab.com/kraxel/qemu into staging (2026-03-10 13:32:30 +) are available in the Git repository at: https://gitlab.com/harshpb/qemu.git tags/pull-ppc-for-11.0-softfreeze-20260310 for you to fetch changes up to 8d00b61217814fa6809768b8d2ca13167ad4106a: MAINTAINERS: Add entry for MPIPL (PowerNV) (2026-03-10 20:23:46 +0530) PPC PR for 11.0 soft-freeze - MPIPL support for PowerNV Hi; this has build failures: https://gitlab.com/qemu-project/qemu/-/jobs/13431423411 ../hw/ppc/pnv_sbe.c:279:29: error: format specifies type 'unsigned long long' but the argument has type 'ram_addr_t' (aka 'unsigned long') [-Werror,-Wformat] 277 | qemu_log_mask(LOG_GUEST_ERROR, | ~~ 278 | "SBE: skiboot_base 0x%" PRIx64 " exceeds RAM size 0x%" PRIx64 "\n", | ~~~ 279 | mbox_val, machine->ram_size); | ~~^~ You need to use RAM_ADDR_FMT for printing ram_addr_t values. https://gitlab.com/qemu-project/qemu/-/jobs/13431423381 In file included from ../hw/ppc/pnv_lpc.c:28: In file included from /tmp/cirrus-ci-build/include/hw/ppc/pnv.h:28: /tmp/cirrus-ci-build/include/hw/ppc/pnv_mpipl.h:54:9: error: '__packed' macro redefined [-Werror,-Wmacro-redefined] 54 | #define __packed __attribute__((packed)) | ^ /usr/include/sys/cdefs.h:217:9: note: previous definition is here 217 | #define __packed __attribute__((__packed__)) | ^ 1 error generated. This header shouldn't be defining its own private macro for the packed attribute -- use QEMU_PACKED. Not a compile error, but I just noticed: This header should not include osdep.h. The rule is: * all .c files include osdep.h first * no .h file includes osdep.h Also, the fadump test failed on the functional-system-centos CI job: https://gitlab.com/qemu-project/qemu/-/jobs/13431423958 AssertionError: 'b'fadump: Reserved '' found in console, expected 'b'fadump: Firmware-assisted dump is active'' thanks -- PMM
Re: [PULL 00/10] PPC PR for 11.0 soft-freeze
On Tue, 10 Mar 2026 at 15:15, Harsh Prateek Bora wrote: > > The following changes since commit ae56950eac7b61b1abf42003329ee0f3ce111711: > > Merge tag 'firmware-20260310-pull-request' of > https://gitlab.com/kraxel/qemu into staging (2026-03-10 13:32:30 +) > > are available in the Git repository at: > > https://gitlab.com/harshpb/qemu.git > tags/pull-ppc-for-11.0-softfreeze-20260310 > > for you to fetch changes up to 8d00b61217814fa6809768b8d2ca13167ad4106a: > > MAINTAINERS: Add entry for MPIPL (PowerNV) (2026-03-10 20:23:46 +0530) > > > PPC PR for 11.0 soft-freeze > > - MPIPL support for PowerNV > Hi; this has build failures: https://gitlab.com/qemu-project/qemu/-/jobs/13431423411 ../hw/ppc/pnv_sbe.c:279:29: error: format specifies type 'unsigned long long' but the argument has type 'ram_addr_t' (aka 'unsigned long') [-Werror,-Wformat] 277 | qemu_log_mask(LOG_GUEST_ERROR, | ~~ 278 | "SBE: skiboot_base 0x%" PRIx64 " exceeds RAM size 0x%" PRIx64 "\n", | ~~~ 279 | mbox_val, machine->ram_size); | ~~^~ You need to use RAM_ADDR_FMT for printing ram_addr_t values. https://gitlab.com/qemu-project/qemu/-/jobs/13431423381 In file included from ../hw/ppc/pnv_lpc.c:28: In file included from /tmp/cirrus-ci-build/include/hw/ppc/pnv.h:28: /tmp/cirrus-ci-build/include/hw/ppc/pnv_mpipl.h:54:9: error: '__packed' macro redefined [-Werror,-Wmacro-redefined] 54 | #define __packed __attribute__((packed)) | ^ /usr/include/sys/cdefs.h:217:9: note: previous definition is here 217 | #define __packed __attribute__((__packed__)) | ^ 1 error generated. This header shouldn't be defining its own private macro for the packed attribute -- use QEMU_PACKED. Not a compile error, but I just noticed: This header should not include osdep.h. The rule is: * all .c files include osdep.h first * no .h file includes osdep.h Also, the fadump test failed on the functional-system-centos CI job: https://gitlab.com/qemu-project/qemu/-/jobs/13431423958 AssertionError: 'b'fadump: Reserved '' found in console, expected 'b'fadump: Firmware-assisted dump is active'' thanks -- PMM
