mirror of
https://github.com/Motorhead1991/qemu.git
synced 2026-01-24 22:17:22 -07:00
fdb87f0dc2
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> |
||
|---|---|---|
| .. | ||
| avocado_qemu | ||
| boot_linux.py | ||
| boot_linux_console.py | ||
| cpu_queries.py | ||
| empty_cpu_model.py | ||
| linux_initrd.py | ||
| linux_ssh_mips_malta.py | ||
| machine_arm_canona1100.py | ||
| machine_arm_integratorcp.py | ||
| machine_arm_n8x0.py | ||
| machine_avr6.py | ||
| machine_m68k_nextcube.py | ||
| machine_mips_malta.py | ||
| machine_rx_gdbsim.py | ||
| machine_sparc64_sun4u.py | ||
| machine_sparc_leon3.py | ||
| migration.py | ||
| pc_cpu_hotplug_props.py | ||
| ppc_prep_40p.py | ||
| README.rst | ||
| replay_kernel.py | ||
| version.py | ||
| virtio_check_params.py | ||
| virtio_version.py | ||
| vnc.py | ||
| x86_cpu_model_versions.py | ||
============================================ Acceptance tests using the Avocado Framework ============================================ This directory contains functional tests, also known as acceptance level tests. They're usually higher level, and may interact with external resources and with various guest operating systems. For more information, please refer to ``docs/devel/testing.rst``, section "Acceptance tests using the Avocado Framework".