1 files changed, 74 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/118/kernel/1885553 b/results/classifier/zero-shot/118/kernel/1885553
new file mode 100644
index 000000000..04145c8a5
--- /dev/null
+++ b/results/classifier/zero-shot/118/kernel/1885553
@@ -0,0 +1,74 @@
+arm: 0.956
+architecture: 0.955
+kernel: 0.930
+graphic: 0.813
+device: 0.780
+files: 0.742
+hypervisor: 0.701
+ppc: 0.690
+debug: 0.680
+PID: 0.677
+user-level: 0.665
+performance: 0.643
+network: 0.628
+semantic: 0.616
+vnc: 0.609
+risc-v: 0.601
+peripherals: 0.577
+socket: 0.574
+register: 0.573
+TCG: 0.573
+x86: 0.564
+VMM: 0.560
+permissions: 0.554
+mistranslation: 0.552
+i386: 0.540
+boot: 0.540
+KVM: 0.476
+assembly: 0.468
+virtual: 0.342
+
+make-check test failed with "Segmentation fault"
+
+While running the make-check testing on arm architecture the test failed with error:
+"kill_qemu() detected QEMU death from signal 11 (Segmentation fault) (core dumped)". Apart from that make-install test always passes.
+The problem doesn't reproduce in 100%
+qemu - from the master branch
+RHEL-8 kernel 4.18.0-221.el8.aarch64
+Logfile with an error you can to find in attachment
+
+Thanks
+
+
+
+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" within the next 60 days (otherwise it will get
+closed as "Expired"). We will then eventually migrate the ticket auto-
+matically to the new system (but you won't be the reporter of the bug
+in the new system and thus 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.]
+