From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu master tests/vmstate prints "Failed to load simple/primitive:b_1" etc
Date: Mon, 17 Oct 2016 19:51:27 +0100 [thread overview]
Message-ID: <20161017185126.GD12934@work-vm> (raw)
In-Reply-To: <CAFEAcA_TwO4Yy0BE8YQFSTNwCOK=+NN2Naz=nZgVjpEM3O7YYQ@mail.gmail.com>
* Peter Maydell (peter.maydell@linaro.org) wrote:
> I've just noticed that qemu master running 'make check' prints
> GTESTER tests/test-vmstate
> Failed to load simple/primitive:b_1
> Failed to load simple/primitive:i64_2
> Failed to load simple/primitive:i32_1
> Failed to load simple/primitive:i32_1
>
> but the test doesn't fail.
>
> Can we either (a) silence this output if it's spurious or (b) have
> it cause the test to fail if it's real (and fix the cause of the
> failure ;-)), please?
The test (has always) tried loading truncated versions of the migration
stream and made sure that it receives an error from vmstate_load_state.
However I just added an error so we can see which field fails to load
in a migration where we just used to get a 'migration has failed with -22'
Is there a way to silence error_report's that's already in use in tests?
Dave
> thanks
> -- PMM
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-10-17 18:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 18:37 [Qemu-devel] qemu master tests/vmstate prints "Failed to load simple/primitive:b_1" etc Peter Maydell
2016-10-17 18:51 ` Dr. David Alan Gilbert [this message]
2016-10-17 19:04 ` Peter Maydell
2016-10-17 19:15 ` Dr. David Alan Gilbert
2016-10-17 21:08 ` Paolo Bonzini
2016-10-18 8:03 ` Markus Armbruster
2016-10-18 9:54 ` Dr. David Alan Gilbert
2016-10-18 13:38 ` Paolo Bonzini
2016-10-20 10:41 ` Dr. David Alan Gilbert
2016-10-24 14:26 ` Paolo Bonzini
2016-10-20 8:41 ` Halil Pasic
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=20161017185126.GD12934@work-vm \
--to=dgilbert@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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.