> -----Original Message----- > From: Peter Maydell <[email protected]> > Sent: 23 January 2026 15:48 > To: Shameer Kolothum <[email protected]> > Cc: Jonathan Cameron <[email protected]>; Eric Auger > <[email protected]>; [email protected]; qemu- > [email protected]; Richard Henderson <[email protected]>; > Jason Gunthorpe <[email protected]>; Nicolin Chen <[email protected]>; > [email protected]; [email protected]; [email protected]; > [email protected]; Nathan Chen <[email protected]>; Matt Ochs > <[email protected]>; [email protected]; [email protected]; > [email protected]; [email protected]; > [email protected]; [email protected]; Krishnakant Jaju > <[email protected]> > Subject: Re: [PATCH v8 00/37] hw/arm/virt: Add support for user-creatable > accelerated SMMUv3 > > On Fri, 23 Jan 2026 at 15:33, Shameer Kolothum > <[email protected]> wrote: > > > stderr: > > > acpi-test: Warning! IORT binary file mismatch. Actual > > > [aml:/tmp/aml-7QQVJ3], Expected > > > [aml:tests/data/acpi/aarch64/virt/IORT.its_off]. > > > > Any way to retrieve these files? > > They aren't in the "job artifacts", but you can probably do > a patch to tweak the CI job to add them, push to your own > gitlab fork of QEMU to have it run the CI, and then look at > the results.
I forked your QEMU GitLab repo and pushed my series here: https://gitlab.com/shamiali2008/qemu/-/commits/target-arm.next-smmuv3-accel However, I am not seeing any CI jobs running on my fork. In the settings it shows no assigned runners under Settings CI/CD/Runners, so it looks like CI is not enabled. TBH, I am not very familiar with GitLab CI, so I may be missing something obvious. I will have another look at the settings... Thanks, Shameer
