From: Thomas Huth <thuth@redhat.com>
To: QEMU Developers <qemu-devel@nongnu.org>,
Subbaraya Sundeep <sundeep.lkml@gmail.com>
Cc: qemu-arm <qemu-arm@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Test failure with Smartfusion2 emac block (msf2-emac)
Date: Tue, 7 Jul 2020 07:18:35 +0200 [thread overview]
Message-ID: <e010da48-cfbe-9616-d750-a922cb463a94@redhat.com> (raw)
Hi Subbaraya,
today, I noticed that there is a test failure with msf2-emac when
running the device-introspect-test in slow mode. Either run:
make check-qtest-aarch64 SPEED=slow
or as a shortcut:
make tests/qtest/device-introspect-test
QTEST_QEMU_BINARY="aarch64-softmmu/qemu-system-aarch64" \
./tests/qtest/device-introspect-test -m slow
Then the test fails with:
Unexpected error in error_set_from_qdev_prop_error() at
hw/core/qdev-properties.c:1251:
Property 'msf2-emac.netdev' can't take value 'hub0port0', it's in use
Could you please have a look?
Thanks,
Thomas
next reply other threads:[~2020-07-07 5:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 5:18 Thomas Huth [this message]
2020-07-07 5:32 ` Test failure with Smartfusion2 emac block (msf2-emac) Thomas Huth
2020-07-14 14:42 ` Philippe Mathieu-Daudé
2020-07-16 2:50 ` sundeep subbaraya
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=e010da48-cfbe-9616-d750-a922cb463a94@redhat.com \
--to=thuth@redhat.com \
--cc=f4bug@amsat.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sundeep.lkml@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).