I suspect the "ERROR: testbed failure: testbed auxverb failed with exit code 255" messages are only the symptom and not the cause of the failures.
All the arm64 failures are consistent and the last tests executed are always the following: [...] 19:05:33 INFO | START ubuntu_kernel_selftests.ftrace ubuntu_kernel_selftests.ftrace timestamp=1600715133 timeout=1800 localtime=Sep 21 19:05:33 [...] 19:06:44 DEBUG| [stdout] # [46] Create/delete multiprobe on kprobe event [PASS] 19:06:46 DEBUG| [stdout] # [47] Kprobe event parser error log check [PASS] 19:06:46 DEBUG| [stdout] # [48] Kretprobe dynamic event with arguments [PASS] 19:06:47 DEBUG| [stdout] # [49] Kretprobe dynamic event with maxactive [PASS] autopkgtest-virt-ssh [19:26:52]: ------- nova console-log 939a7972-4eb7-4814-a489-046ce015ad8e (adt-groovy-arm64-linux-20200921-123119) ------ [...] >From comment #2 on bug 1549425: "The auxverb is "ssh" in this case, and it exiting with 255 means that the ssh connection was interrupted." So I suspect some ftrace test is causing a kernel hang, killing the ssh connection. I don't see anything suspicious on the adt console logs though. We might need to try to reproduce this manually to get some more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918226 Title: testbed auxverb failed with exit code 255 with linux on Groovy ADT failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918226/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
