diff options
Diffstat (limited to 'results/classifier/zero-shot/108/other/1901068')
| -rw-r--r-- | results/classifier/zero-shot/108/other/1901068 | 60 |
1 files changed, 60 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1901068 b/results/classifier/zero-shot/108/other/1901068 new file mode 100644 index 000000000..c36205a81 --- /dev/null +++ b/results/classifier/zero-shot/108/other/1901068 @@ -0,0 +1,60 @@ +device: 0.878 +files: 0.813 +graphic: 0.756 +other: 0.751 +performance: 0.674 +PID: 0.651 +debug: 0.639 +permissions: 0.636 +network: 0.636 +vnc: 0.617 +semantic: 0.613 +socket: 0.542 +KVM: 0.508 +boot: 0.418 + +Deleted tests are still run if they exist in the build tree + +Steps to reproduce: +1. Add a new device along with a qtest to exercise it. +2. Run make check-qtest. It passes. +3. Revert the commit that added the device and qtest. +4. Run make check-qtest again. It now fails because the device no longer exists, but the test is somehow still there even though the source files are gone and it's not mentioned in tests/qtest/meson.build. + +After running make clean, make check-qtest passes again. + +$ git describe +v5.1.0-2465-g4c5b97bfd0 + +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" or "Confirmed" within the next 60 days (other- +wise it will get closed as "Expired"). We will then eventually migrate +the ticket automatically to the new system (but you won't be the reporter +of the bug in the new system and thus you 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.] + |