[Bug 1918226] Re: testbed auxverb failed with exit code 255 with linux on Groovy ADT failure
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Won't Fix -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918226] Re: testbed auxverb failed with exit code 255 with linux on Groovy ADT failure
** Tags added: i386 -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918226] Re: testbed auxverb failed with exit code 255 with linux on Groovy ADT failure
I also looked at this and compared with older kernels. This test has never progressed past the "Kretprobe dynamic event with maxactive" test on 5.8, but it has on 5.4: ``` 18:41:31 DEBUG| [stdout] # [43] Kprobe event parser error log check [PASS] 18:41:32 DEBUG| [stdout] # [44] Kretprobe dynamic event with arguments [PASS] 18:41:33 DEBUG| [stdout] # [45] Kretprobe dynamic event with maxactive [PASS] 18:41:49 DEBUG| [stdout] # [46] Register/unregister many kprobe events [PASS] 18:41:49 DEBUG| [stdout] # [47] Kprobe dynamic event - adding and removing [PASS] 18:41:50 DEBUG| [stdout] # [48] Uprobe event parser error log check [PASS] 18:41:50 DEBUG| [stdout] # [49] test for the preemptirqsoff tracer [UNSUPPORTED] 18:42:32 DEBUG| [stdout] # [50] Meta-selftest [PASS] ``` I suspect that next test is causing a hang and ssh dies. The autopkgtest infrastructure sees this and tries to provide some debugging info (the console log and vm details). -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918226] Re: testbed auxverb failed with exit code 255 with linux on Groovy ADT failure
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=1600715133timeout=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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918226] Re: testbed auxverb failed with exit code 255 with linux on Groovy ADT failure
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
