add 18th iteration of classifier

1 files changed, 62 insertions, 0 deletions

diff --git a/results/classifier/118/arm/633 b/results/classifier/118/arm/633
new file mode 100644
index 000000000..9ff3230c0
--- /dev/null
+++ b/results/classifier/118/arm/633
@@ -0,0 +1,62 @@
+arm: 0.901
+device: 0.874
+PID: 0.839
+debug: 0.806
+i386: 0.784
+permissions: 0.765
+x86: 0.746
+ppc: 0.740
+graphic: 0.704
+performance: 0.688
+kernel: 0.670
+socket: 0.657
+assembly: 0.625
+semantic: 0.620
+VMM: 0.615
+risc-v: 0.556
+KVM: 0.545
+boot: 0.525
+network: 0.520
+user-level: 0.519
+architecture: 0.505
+vnc: 0.488
+hypervisor: 0.451
+TCG: 0.445
+mistranslation: 0.443
+register: 0.442
+virtual: 0.431
+files: 0.396
+peripherals: 0.364
+
+i686-arm-user-static - Allocating guest commpage: Operation not permitted
+Steps to reproduce:
+1. Run the test case linked earlier.
+2. You'll see `apt update` failing:
+
+```
+Get:1 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB]
+Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
+Err:1 http://archive.raspberrypi.org/debian buster InRelease
+  At least one invalid signature was encountered.
+Err:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
+  At least one invalid signature was encountered.
+Reading package lists... Done
+W: GPG error: http://archive.raspberrypi.org/debian buster InRelease: At least one invalid signature was encountered.
+E: The repository 'http://archive.raspberrypi.org/debian buster InRelease' is not signed.
+N: Updating from such a repository can't be done securely, and is therefore disabled by default.
+N: See apt-secure(8) manpage for repository creation and user configuration details.
+W: GPG error: http://raspbian.raspberrypi.org/raspbian buster InRelease: At least one invalid signature was encountered.
+E: The repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' is not signed.
+N: Updating from such a repository can't be done securely, and is therefore disabled by default.
+N: See apt-secure(8) manpage for repository creation and user configuration details.
+```
+Additional information:
+Setting `sysctl vm.mmap_min_addr=53248` makes it work (as opposed to the system default of 65536).
+
+Bisecting the bug linked earlier also breaks this in a slightly different way. Everything works at 87b74e8b6edd287ea2160caa0ebea725fa8f1ca1. After that, apt update appears to work, but the package lists end up empty, so nothing can be installed. Then after 975ac4559c4c00010e05f7a3e782eeb9497837ea, the output is as provided above.
+
+apt launches /usr/lib/apt/methods/gpgv and passes it some commands through stdin. gpgv launches /usr/bin/apt-key, which fails with `Allocating guest commpage: Operation not permitted`. Running gpgv directly and sending the same commands works without any issues. The problem only occurs when gpgv is run through apt. (I don't meant the normal system gpgv binary, but the transport method binary that comes with apt)
+
+Getting any output is tricky because by the time apt-key is launched, gpgv redirects stdout and stderr to /dev/null and communication takes place through fd 3. https://salsa.debian.org/apt-team/apt/-/blob/2.2.4/apt-pkg/contrib/gpgv.cc#L355 https://salsa.debian.org/apt-team/apt/-/blob/main/methods/gpgv.cc#L186
+
+I had to do some ugly things with different versions of qemu and wrapper scripts to see the commpage error, but hopefully there's enough information provided here that it won't be necessary.