blob: 379ff21062f8a62f835d4bcec3f8edd8ca2810a9 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
PID: 0.996
other: 0.996
files: 0.993
semantic: 0.984
performance: 0.983
socket: 0.980
graphic: 0.980
device: 0.975
debug: 0.970
vnc: 0.940
KVM: 0.932
permissions: 0.930
network: 0.929
boot: 0.810
qtest failures leave orphaned qemu processes hanging around
If a qtest test case fails, it leaves orphaned qemu processes hanging around. On Fedora 18 with qemu.git as of today ( Feb 26 2013), the patch just forces a test failure
ps axwww | grep qemu | grep -v grep
$ make check-qtest-x86_64
CC tests/rtc-test.o
LINK tests/rtc-test
GTESTER check-qtest-x86_64
$ ps axwww | grep qemu | grep -v grep
$ patch -p1 < force-test-failure.patch
patching file tests/rtc-test.c
$ make check-qtest-x86_64
CC tests/rtc-test.o
LINK tests/rtc-test
GTESTER check-qtest-x86_64
**
ERROR:tests/rtc-test.c:256:bcd_check_time: assertion failed: (0)
GTester: last random seed: R02Sf2521dda395a2713128e0cbf86651a21
make: *** [check-qtest-x86_64] Error 1
$ ps axwww | grep qemu | grep -v grep
26258 pts/0 Sl 0:00 x86_64-softmmu/qemu-system-x86_64 -qtest unix:/tmp/qtest-26256.sock,nowait -qtest-log /dev/null -qmp unix:/tmp/qtest-26256.qmp,nowait -pidfile /tmp/qtest-26256.pid -machine accel=qtest -display none -rtc clock=vm
The problem is that an assertion failure in a test case causes the test program to exit(2) without hitting the qtest cleanup.
I think this has been fixed sometime in the past already. Or can you still reproduce this problem with the latest version of QEMU?
It appears this is fixed, I haven't seen it in a while
|