diff options
Diffstat (limited to 'results/classifier/zero-shot/108/other/1557')
| -rw-r--r-- | results/classifier/zero-shot/108/other/1557 | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1557 b/results/classifier/zero-shot/108/other/1557 new file mode 100644 index 000000000..06ded4f38 --- /dev/null +++ b/results/classifier/zero-shot/108/other/1557 @@ -0,0 +1,26 @@ +graphic: 0.759 +device: 0.747 +performance: 0.531 +semantic: 0.447 +debug: 0.396 +network: 0.372 +vnc: 0.256 +PID: 0.225 +socket: 0.213 +files: 0.205 +permissions: 0.163 +boot: 0.132 +other: 0.057 +KVM: 0.037 + +qemu-binfmt-conf.sh handles errors inconsistently +Description of problem: +We are installing qemu via multiarch/qemu-user-static docker image. https://github.com/multiarch/qemu-user-static + +What we have noticed is that because qemu-binfmt-conf.sh does not use `set -e`, its behavior with regards to failures is inconsistent. In short, registering the same thing into binfmt twice is an error (you get EEXIST). However, the exit code of qemu-binfmt-conf.sh itself seems to depend only on whether the last interpreter succeeded, leading to confusing and inconsistent results. +Steps to reproduce: +1. Register only qemu-arm-static interpreter with binfmt. +2. Run qemu-binfmt-conf.sh. Observe that the exit code is zero, and logs show the duplicate interpreter was rejected. +3. Remove all qemu interpreters. +3. Register only qemu-loongarch64-static interpreter (currently last in qemu_target_list) with binfmt. +3. Run qemu-binfmt-conf.sh. Observe that the exit code is non-zero, and logs show the duplicate interpreter was rejected. |