5 files changed, 198 insertions, 0 deletions
diff --git a/results/classifier/118/device/290 b/results/classifier/118/device/290
new file mode 100644
index 00000000..2c6d2604
--- /dev/null
+++ b/results/classifier/118/device/290
@@ -0,0 +1,31 @@
+device: 0.804
+architecture: 0.794
+performance: 0.607
+graphic: 0.600
+network: 0.423
+arm: 0.390
+x86: 0.234
+i386: 0.225
+ppc: 0.223
+VMM: 0.169
+boot: 0.148
+KVM: 0.140
+peripherals: 0.128
+debug: 0.125
+vnc: 0.109
+TCG: 0.105
+risc-v: 0.097
+semantic: 0.073
+hypervisor: 0.063
+mistranslation: 0.060
+user-level: 0.060
+kernel: 0.036
+virtual: 0.027
+assembly: 0.017
+socket: 0.011
+files: 0.011
+PID: 0.010
+permissions: 0.010
+register: 0.006
+
+mmap MAP_NORESERVE of 2^42 bytes consumes 16Gb of actual RAM
diff --git a/results/classifier/118/device/2902 b/results/classifier/118/device/2902
new file mode 100644
index 00000000..f323f2ea
--- /dev/null
+++ b/results/classifier/118/device/2902
@@ -0,0 +1,41 @@
+device: 0.869
+performance: 0.845
+graphic: 0.763
+debug: 0.479
+files: 0.395
+semantic: 0.330
+i386: 0.253
+x86: 0.246
+permissions: 0.191
+vnc: 0.188
+boot: 0.134
+ppc: 0.132
+PID: 0.128
+TCG: 0.123
+risc-v: 0.120
+user-level: 0.092
+architecture: 0.069
+arm: 0.065
+virtual: 0.063
+mistranslation: 0.051
+network: 0.039
+register: 0.035
+peripherals: 0.026
+socket: 0.017
+assembly: 0.017
+hypervisor: 0.012
+VMM: 0.008
+KVM: 0.003
+kernel: 0.002
+
+Data Race with slh_first Field in test-aio-multithread
+Description of problem:
+Potential data races in the `QSLIST_INSERT_HEAD_ATOMIC` macro were identified using TSAN.
+Steps to reproduce:
+```sh
+QEMU_BUILD_DIR=<path to the QEMU build directory>
+QEMU_DIR=<path to the QEMU repository directory>
+configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp
+make tests/unit/test-bdrv-drain
+MALLOC_PERTURB_=102 G_TEST_SRCDIR=$QEMU_BUILD_DIR/tests/unit G_TEST_BUILDDIR=$QEMU_BUILD_DIR/tests/unit $QEMU_BUILD_DIR/tests/unit/test-aio-multithread --tap -k
+```
diff --git a/results/classifier/118/device/2904 b/results/classifier/118/device/2904
new file mode 100644
index 00000000..0d37c6ce
--- /dev/null
+++ b/results/classifier/118/device/2904
@@ -0,0 +1,41 @@
+device: 0.880
+performance: 0.880
+graphic: 0.677
+debug: 0.665
+files: 0.606
+boot: 0.479
+network: 0.450
+vnc: 0.409
+i386: 0.383
+x86: 0.373
+semantic: 0.363
+ppc: 0.349
+permissions: 0.326
+arm: 0.326
+PID: 0.287
+TCG: 0.281
+risc-v: 0.206
+socket: 0.169
+architecture: 0.164
+user-level: 0.160
+register: 0.108
+mistranslation: 0.093
+peripherals: 0.077
+virtual: 0.074
+VMM: 0.065
+kernel: 0.059
+assembly: 0.045
+hypervisor: 0.038
+KVM: 0.020
+
+Data Race in data->cb() call and cb assignment in test-aio-multithread
+Description of problem:
+Potential data races between the `data->cb()` call and the assignment of `cb` in `test-aio-multithread` were identified using TSAN.
+Steps to reproduce:
+```sh
+QEMU_BUILD_DIR=<path to the QEMU build directory>
+QEMU_DIR=<path to the QEMU repository directory>
+configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp
+make tests/unit/test-bdrv-drain
+MALLOC_PERTURB_=102 G_TEST_SRCDIR=$QEMU_BUILD_DIR/tests/unit G_TEST_BUILDDIR=$QEMU_BUILD_DIR/tests/unit $QEMU_BUILD_DIR/tests/unit/test-aio-multithread --tap -k
+```
diff --git a/results/classifier/118/device/2905 b/results/classifier/118/device/2905
new file mode 100644
index 00000000..9b2b62aa
--- /dev/null
+++ b/results/classifier/118/device/2905
@@ -0,0 +1,54 @@
+device: 0.941
+graphic: 0.933
+architecture: 0.917
+debug: 0.914
+socket: 0.898
+performance: 0.862
+register: 0.852
+x86: 0.839
+ppc: 0.832
+vnc: 0.820
+network: 0.735
+semantic: 0.725
+files: 0.720
+risc-v: 0.668
+permissions: 0.619
+peripherals: 0.607
+TCG: 0.606
+PID: 0.581
+kernel: 0.520
+VMM: 0.500
+arm: 0.470
+assembly: 0.459
+user-level: 0.399
+boot: 0.379
+i386: 0.317
+mistranslation: 0.315
+hypervisor: 0.302
+virtual: 0.301
+KVM: 0.082
+
+Windows Curses Display Infinite Loop
+Description of problem:
+The out-of-the-box `qemu-system-x86_64 -display curses` on Windows loops forever while displaying "VGA Blank Mode" instead of booting like `qemu-system-x86_64` does.
+
+This is caused by an infinite loop in the below simplified code in `curses_refresh` in `ui/curses.c`:
+```
+    int chr;
+    // ...trimmed
+    while (1) {
+        /* while there are any pending key strokes to process */
+        chr = console_getch(&maybe_keycode);
+
+        if (chr == -1) 
+            break;
+    // ...trimmed
+    }
+```
+`console_getch` has return type `wint_t`. However, on Windows, `wint_t` is `unsigned short`. Therefore when `console_getch` returns -1, the -1 value of `unsigned short` will be silently converted into the `int` value 65535. This causes `65535 == -1` to always be false, and the loop will never break. I can send a patch to qemu-devel which retypes `chr` to `wint_t` and replaces occurences of -1 with `WEOF` (an alias for `(wint_t) -1`).
+Steps to reproduce:
+1. Install `qemu-w64-setup-20250326.exe` Windows qemu from https://qemu.weilnetz.de/w64/2025/
+2. Run `./qemu-system-x86_64 -display curses`
+3. "VGA Blank Mode" will appear on the screen forever
+Additional information:
+
diff --git a/results/classifier/118/device/2907 b/results/classifier/118/device/2907
new file mode 100644
index 00000000..240d4980
--- /dev/null
+++ b/results/classifier/118/device/2907
@@ -0,0 +1,31 @@
+device: 0.916
+arm: 0.815
+network: 0.815
+kernel: 0.749
+VMM: 0.709
+vnc: 0.700
+ppc: 0.692
+socket: 0.673
+architecture: 0.663
+debug: 0.663
+performance: 0.620
+TCG: 0.596
+risc-v: 0.592
+boot: 0.488
+permissions: 0.451
+PID: 0.444
+files: 0.408
+register: 0.399
+graphic: 0.386
+assembly: 0.307
+semantic: 0.281
+peripherals: 0.197
+user-level: 0.122
+mistranslation: 0.101
+hypervisor: 0.082
+virtual: 0.050
+i386: 0.018
+KVM: 0.007
+x86: 0.003
+
+replay_mutex_unlock() assertion on macOS