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.
** 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
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
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
** 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
