1 files changed, 51 insertions, 0 deletions
diff --git a/results/classifier/118/vnc/1453612 b/results/classifier/118/vnc/1453612
new file mode 100644
index 000000000..60cfa1ba8
--- /dev/null
+++ b/results/classifier/118/vnc/1453612
@@ -0,0 +1,51 @@
+vnc: 0.963
+graphic: 0.690
+device: 0.683
+socket: 0.658
+network: 0.550
+performance: 0.513
+register: 0.488
+risc-v: 0.474
+VMM: 0.455
+architecture: 0.439
+i386: 0.424
+mistranslation: 0.414
+permissions: 0.405
+user-level: 0.393
+hypervisor: 0.380
+PID: 0.376
+semantic: 0.357
+files: 0.357
+x86: 0.356
+debug: 0.350
+ppc: 0.332
+peripherals: 0.323
+boot: 0.279
+arm: 0.261
+virtual: 0.209
+TCG: 0.167
+kernel: 0.146
+assembly: 0.145
+KVM: 0.141
+
+set_password command of monitor has poor feedback on failure
+
+running `set_password vnc NkkmEz5icvTAGo6MECzBVEUxP` in qemu monitor started with `-monitor stdio` gives feedback `Could not set password` which is unhelpful because it doesn't specify the reason of the failure.
+
+experienced with 2.3.0
+
+The QEMU project is currently considering to move 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 older bugs to
+"Incomplete" now.
+
+If you still think this bug report here is valid, then please switch
+the state back to "New" within the next 60 days, otherwise this report
+will be marked as "Expired". Or please mark it as "Fix Released" if
+the problem has been solved with a newer version of QEMU already.
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+