1 files changed, 80 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/1925109 b/results/classifier/118/graphic/1925109
new file mode 100644
index 000000000..c4bcd5802
--- /dev/null
+++ b/results/classifier/118/graphic/1925109
@@ -0,0 +1,80 @@
+graphic: 0.854
+semantic: 0.826
+device: 0.819
+architecture: 0.818
+mistranslation: 0.808
+peripherals: 0.800
+x86: 0.789
+files: 0.789
+performance: 0.786
+user-level: 0.785
+debug: 0.760
+network: 0.740
+permissions: 0.734
+assembly: 0.731
+kernel: 0.729
+PID: 0.723
+hypervisor: 0.703
+arm: 0.702
+ppc: 0.688
+boot: 0.654
+socket: 0.641
+virtual: 0.634
+register: 0.634
+risc-v: 0.608
+VMM: 0.587
+vnc: 0.583
+TCG: 0.562
+i386: 0.559
+KVM: 0.557
+
+usbredirparser: bulk transfer length exceeds limits
+
+2021-04-20T01:26:36.662244Z qemu-system-x86_64: usbredirparser: bulk transfer length exceeds limits 131072 > 65536
+2021-04-20T01:26:36.662276Z qemu-system-x86_64: usbredirparser: error usbredirparser_send_* call invalid params, please report!!
+2021-04-20T01:26:57.670412Z qemu-system-x86_64: usbredirparser: bulk transfer length exceeds limits 131072 > 65536
+2021-04-20T01:26:57.670445Z qemu-system-x86_64: usbredirparser: error usbredirparser_send_* call invalid params, please report!!
+2021-04-20T01:37:01.920613Z qemu-system-x86_64: usbredirparser: bulk transfer length exceeds limits 131072 > 65536
+2021-04-20T01:37:01.920624Z qemu-system-x86_64: usbredirparser: error usbredirparser_send_* call invalid params, please report!!
+host:
+Linux version 5.11.15-arch1-2 (linux@archlinux) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Sat, 17 Apr 2021 00:22:30 +0000
+guest:
+win10 20H2
+usb device:
+Bus 002 Device 007: ID 0781:55ab SanDisk Corp.  SanDisk 3.2Gen1
+size 250G
+
+https://gitlab.freedesktop.org/spice/usbredir/-/blob/master/usbredirparser/usbredirparser.c#L32
+
+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.]
+