summary refs log tree commit diff stats
path: root/results/classifier/105/other/1915431
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-03 12:04:13 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-03 12:04:13 +0000
commit256709d2eb3fd80d768a99964be5caa61effa2a0 (patch)
tree05b2352fba70923126836a64b6a0de43902e976a /results/classifier/105/other/1915431
parent2ab14fa96a6c5484b5e4ba8337551bb8dcc79cc5 (diff)
downloadqemu-analysis-256709d2eb3fd80d768a99964be5caa61effa2a0.tar.gz
qemu-analysis-256709d2eb3fd80d768a99964be5caa61effa2a0.zip
add new classifier result
Diffstat (limited to 'results/classifier/105/other/1915431')
-rw-r--r--results/classifier/105/other/191543157
1 files changed, 57 insertions, 0 deletions
diff --git a/results/classifier/105/other/1915431 b/results/classifier/105/other/1915431
new file mode 100644
index 000000000..1c55088a8
--- /dev/null
+++ b/results/classifier/105/other/1915431
@@ -0,0 +1,57 @@
+other: 0.747
+graphic: 0.622
+semantic: 0.570
+network: 0.561
+device: 0.544
+mistranslation: 0.531
+assembly: 0.490
+instruction: 0.469
+socket: 0.461
+vnc: 0.428
+KVM: 0.397
+boot: 0.276
+
+QEMU processes started by Acceptance Tests are left running
+
+Every now and then, QEMU processes started by the Acceptance Tests (thus by Avocado) will be left running.
+
+From Avocado's perspective, when everything "goes well" and a test reaches completion, there's no attempt to terminate any processes it indirectly started.  Some frameworks and tests built on top of Avocado, for instance Avocado-VT, will keep processes running between various tests.
+
+When a job (and consequently a test) is manually interrupted, then Avocado tries to terminate the entire process tree. 
+
+It may be possible to improve the situation in which, at the very least, the user is:
+ * notified of left over processes
+ * have a configuration option that will attempt to kill all processes at the end of the test execution
+
+The QEMU project is currently moving its bug tracking to another system.
+For this we need to know which bugs are still valid and which could be
+closed already. Thus we are setting the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" or "Confirmed" within the next 60 days (other-
+wise it will get closed as "Expired"). We will then eventually migrate
+the ticket automatically to the new system (but you won't be the reporter
+of the bug in the new system and thus you won't get notified on changes
+anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+