On Tue, 3 Mar 2026 at 15:07, Daniel P. Berrangé <[email protected]> wrote: > > The following changes since commit 3fb456e9a0e9eef6a71d9b49bfff596a0f0046e9: > > Merge tag 'pull-request-2026-03-02' of https://gitlab.com/thuth/qemu into > staging (2026-03-02 14:01:46 +0000) > > are available in the Git repository at: > > https://gitlab.com/berrange/qemu tags/next-pr-pull-request > > for you to fetch changes up to 192f59773a6a8fd1e0d3c1d9c9c3f5f59a62c087: > > util/oslib-posix: increase memprealloc thread count to 32 (2026-03-03 > 15:01:21 +0000) > > ---------------------------------------------------------------- > * Increase pre-alloc max thread count to 32 > * Fix checkpatch warning for new/removed files with --terse > * Detect more GPL boilerplate in checkpatch > * Fix lean of data in TLS/websock GSource cancellation > * Tweak CPU docs for DiamondRapids > * Unconditionally enable thread naming > * Fix race setting thread naming on Win32 > * Add API docs for logging APIs > * Fix interleaved error/trace output > * Fix missing error prefixes with warn_report > * Add detailed error reporting for VNC passworrd changes > * Refactoring of error_vprintf & related funcs > > ----------------------------------------------------------------
Something in this consistently causes the s390x runner to fail the test-migration test: https://gitlab.com/qemu-project/qemu/-/jobs/13367184083 https://gitlab.com/qemu-project/qemu/-/jobs/13366572115 https://gitlab.com/qemu-project/qemu/-/jobs/13339069533 https://gitlab.com/qemu-project/qemu/-/jobs/13336989367 This was a CI run together with the loongarch pullreq, but that has just passed this job when run in CI on its own: https://gitlab.com/qemu-project/qemu/-/jobs/13367800326 so it seems like this pullreq is the one causing the s390x failures. thanks -- PMM
