1 files changed, 104 insertions, 0 deletions
diff --git a/results/classifier/118/review/1915431 b/results/classifier/118/review/1915431
new file mode 100644
index 00000000..105a807f
--- /dev/null
+++ b/results/classifier/118/review/1915431
@@ -0,0 +1,104 @@
+user-level: 0.807
+architecture: 0.694
+performance: 0.645
+graphic: 0.622
+hypervisor: 0.619
+semantic: 0.570
+permissions: 0.568
+network: 0.561
+files: 0.559
+device: 0.544
+register: 0.536
+mistranslation: 0.531
+debug: 0.522
+PID: 0.491
+assembly: 0.490
+peripherals: 0.482
+ppc: 0.475
+socket: 0.461
+VMM: 0.450
+TCG: 0.446
+kernel: 0.436
+i386: 0.433
+vnc: 0.428
+x86: 0.413
+KVM: 0.397
+risc-v: 0.373
+virtual: 0.372
+arm: 0.370
+boot: 0.276
+--------------------
+x86: 0.081
+debug: 0.075
+TCG: 0.066
+virtual: 0.065
+user-level: 0.065
+PID: 0.049
+performance: 0.042
+hypervisor: 0.030
+semantic: 0.024
+files: 0.019
+device: 0.014
+i386: 0.014
+network: 0.013
+ppc: 0.009
+register: 0.005
+arm: 0.005
+peripherals: 0.005
+boot: 0.005
+assembly: 0.004
+architecture: 0.004
+risc-v: 0.004
+kernel: 0.003
+permissions: 0.003
+socket: 0.002
+graphic: 0.002
+vnc: 0.002
+VMM: 0.001
+mistranslation: 0.001
+KVM: 0.000
+
+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.]
+