All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>,
	Thomas Huth <thuth@redhat.com>
Subject: Re: [PULL 00/17] Migration patches for 2024-12-17
Date: Thu, 19 Dec 2024 15:53:22 -0300	[thread overview]
Message-ID: <87zfkrtsgt.fsf@suse.de> (raw)
In-Reply-To: <20241219123213.GA692742@fedora>

Stefan Hajnoczi <stefanha@redhat.com> writes:

> Hi Fabiano,
> Please take a look at this CI failure:
>
>>>> MALLOC_PERTURB_=61 QTEST_QEMU_BINARY=./qemu-system-s390x UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 QTEST_QEMU_IMG=./qemu-img MESON_TEST_ITERATION=1 MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 PYTHON=/home/gitlab-runner/builds/4S3awx_3/0/qemu-project/qemu/build/pyvenv/bin/python3 QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-storage-daemon G_TEST_DBUS_DAEMON=/home/gitlab-runner/builds/4S3awx_3/0/qemu-project/qemu/tests/dbus-vmstate-daemon.sh /home/gitlab-runner/builds/4S3awx_3/0/qemu-project/qemu/build/tests/qtest/migration-test --tap -k
> ――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――
> stderr:
> Traceback (most recent call last):
>   File "/home/gitlab-runner/builds/4S3awx_3/0/qemu-project/qemu/build/scripts/analyze-migration.py", line 688, in <module>
>     dump.read(dump_memory = args.memory)
>   File "/home/gitlab-runner/builds/4S3awx_3/0/qemu-project/qemu/build/scripts/analyze-migration.py", line 625, in read
>     section.read()
>   File "/home/gitlab-runner/builds/4S3awx_3/0/qemu-project/qemu/build/scripts/analyze-migration.py", line 461, in read
>     field['data'] = reader(field, self.file)
>   File "/home/gitlab-runner/builds/4S3awx_3/0/qemu-project/qemu/build/scripts/analyze-migration.py", line 434, in __init__
>     for field in self.desc['struct']['fields']:
> KeyError: 'fields'

This is the command line that runs only this specific test:

PYTHON=/usr/bin/python3.11 QTEST_QEMU_BINARY=./qemu-system-s390x
./tests/qtest/migration-test -p /s390x/migration/analyze-script

I cannot reproduce in migration-next nor in the detached HEAD that the
pipeline ran in (had to download the tarball from gitlab).

The only s390 patch in this PR is one that I can test just fine with
TCG, so there shouldn't be any difference from KVM (i.e. there should be
no state being migrated with KVM that is not already migrated with TCG).

> warning: fd: migration to a file is deprecated. Use file: instead.
> warning: fd: migration to a file is deprecated. Use file: instead.

This is harmless.

> **
> ERROR:../tests/qtest/migration-test.c:36:main: assertion failed (ret == 0): (1 == 0)
> (test program exited with status code -6)

This is the assert at the end of the tests, irrelevant.

>
> https://gitlab.com/qemu-project/qemu/-/jobs/8681858344#L8190
>
> If you find this pull request caused the failure, please send a new
> revision. Otherwise please let me know so we can continue to
> investigate.

I don't have an s390x host at hand so the only thing I can to is to drop
that patch and hope that resolves the problem. @Peter, @Thomas, any
other ideas? Can you verify this on your end?


  reply	other threads:[~2024-12-19 18:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 17:48 [PULL 00/17] Migration patches for 2024-12-17 Fabiano Rosas
2024-12-17 17:48 ` [PULL 01/17] migration/multifd: Fix compile error caused by page_size usage Fabiano Rosas
2024-12-17 17:48 ` [PULL 02/17] migration/multifd: Further remove the SYNC on complete Fabiano Rosas
2024-12-17 17:48 ` [PULL 03/17] migration/multifd: Allow to sync with sender threads only Fabiano Rosas
2024-12-17 17:48 ` [PULL 04/17] migration/ram: Move RAM_SAVE_FLAG* into ram.h Fabiano Rosas
2024-12-17 17:48 ` [PULL 05/17] migration/multifd: Unify RAM_SAVE_FLAG_MULTIFD_FLUSH messages Fabiano Rosas
2024-12-17 17:48 ` [PULL 06/17] migration/multifd: Remove sync processing on postcopy Fabiano Rosas
2024-12-17 17:48 ` [PULL 07/17] migration/multifd: Cleanup src flushes on condition check Fabiano Rosas
2024-12-17 17:48 ` [PULL 08/17] migration/multifd: Document the reason to sync for save_setup() Fabiano Rosas
2024-12-17 17:48 ` [PULL 09/17] migration/multifd: Fix compat with QEMU < 9.0 Fabiano Rosas
2024-12-17 17:48 ` [PULL 10/17] s390x: Fix CSS migration Fabiano Rosas
2024-12-17 17:48 ` [PULL 11/17] migration: Add helper to get target runstate Fabiano Rosas
2024-12-17 17:48 ` [PULL 12/17] qmp/cont: Only activate disks if migration completed Fabiano Rosas
2024-12-17 17:48 ` [PULL 13/17] migration/block: Make late-block-active the default Fabiano Rosas
2024-12-17 17:48 ` [PULL 14/17] migration/block: Apply late-block-active behavior to postcopy Fabiano Rosas
2024-12-17 17:48 ` [PULL 15/17] migration/block: Fix possible race with block_inactive Fabiano Rosas
2024-12-17 17:48 ` [PULL 16/17] migration/block: Rewrite disk activation Fabiano Rosas
2024-12-17 17:48 ` [PULL 17/17] tests/qtest/migration: Fix compile errors when CONFIG_UADK is set Fabiano Rosas
2024-12-19 12:32 ` [PULL 00/17] Migration patches for 2024-12-17 Stefan Hajnoczi
2024-12-19 18:53   ` Fabiano Rosas [this message]
2024-12-20 16:28     ` Peter Xu
2025-01-02  9:32       ` Thomas Huth
2025-01-03 18:30         ` Fabiano Rosas
2025-01-03 20:31           ` Stefan Hajnoczi
2025-01-03 21:00             ` Fabiano Rosas
2025-01-03 22:34               ` Fabiano Rosas
2025-01-06 18:45                 ` Peter Xu
2025-01-06 19:24                   ` Fabiano Rosas
2025-01-06 20:22                     ` Peter Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zfkrtsgt.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.