summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/108/none/1793539
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/zero-shot/108/none/1793539')
-rw-r--r--results/classifier/zero-shot/108/none/179353931
1 files changed, 31 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/none/1793539 b/results/classifier/zero-shot/108/none/1793539
new file mode 100644
index 000000000..3ef224c38
--- /dev/null
+++ b/results/classifier/zero-shot/108/none/1793539
@@ -0,0 +1,31 @@
+device: 0.311
+graphic: 0.284
+semantic: 0.182
+other: 0.089
+PID: 0.062
+socket: 0.061
+performance: 0.057
+vnc: 0.056
+permissions: 0.039
+debug: 0.033
+network: 0.026
+boot: 0.021
+files: 0.014
+KVM: 0.002
+
+qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6003ddc5
+
+During the build of gedit for RISC-V this error occurs:
+
+$ qemu-riscv64 -E LD_LIBRARY_PATH=gedit/.libs ./gedit/.libs/gedit
+qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6003ddc5
+qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x600009e4
+
+https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/gedit/standard/riscv64
+
+Possibly duplicate of bug #1594394, in which case it would be worth testing with 5.0.0 or above..
+
+Actually more likely https://github.com/vivier/qemu-m68k/issues/33, in which case it's also fixed..
+
+As you can see in the build log the package builds sucessfully.
+