diff options
| author | John Snow <jsnow@redhat.com> | 2020-07-10 01:06:46 -0400 |
|---|---|---|
| committer | Philippe Mathieu-Daudé <philmd@redhat.com> | 2020-07-14 22:22:22 +0200 |
| commit | fdb87f0dc2ed8e4f712a88fb5f9382ceea620223 (patch) | |
| tree | 1c48996f587608d3754a98bf7f4df69278563161 /net/tap-bsd.c | |
| parent | a0690c39006b897d6453daf591909948ac553650 (diff) | |
| download | qemu-fdb87f0dc2ed8e4f712a88fb5f9382ceea620223.zip qemu-fdb87f0dc2ed8e4f712a88fb5f9382ceea620223.tar.gz qemu-fdb87f0dc2ed8e4f712a88fb5f9382ceea620223.tar.bz2 | |
tests/acceptance: Don't test reboot on cubieboard
cubieboard does not have a functioning reboot, it halts and QEMU does
not exit.
vm.shutdown() is modified in a forthcoming patch that makes it less tolerant
of race conditions on shutdown; tests should consciously decide to WAIT
or to SHUTDOWN qemu.
So long as this test is attempting to reboot, the correct choice would
be to WAIT for the VM to exit. However, since that's broken, we should
SHUTDOWN instead.
SHUTDOWN is indeed what already happens when the test performs teardown,
however, if anyone fixes cubieboard reboot in the future, this test will
develop a new race condition that might be hard to debug.
Therefore: remove the reboot test and make it obvious that the VM is
still running when the test concludes, where the test teardown will do
the right thing.
Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Cleber Rosa <crosa@redhat.com>
Tested-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20200710050649.32434-10-jsnow@redhat.com>
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Diffstat (limited to 'net/tap-bsd.c')
0 files changed, 0 insertions, 0 deletions