-
Notifications
You must be signed in to change notification settings - Fork 730
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: tests crash with exit code 42 #598
Comments
I've been banging my head against this for a while, and finally made some progress. I enabled tracing of the
This means digging into what's happening in the kernel. Using
|
Sent an email to the KVM mailing list: https://lore.kernel.org/kvm/95c1dc01-4aa0-46a6-95b1-bbc62588ac6e@www.fastmail.com/T/#u |
No takers on the mailing list unfortunately, I've decided to report with ubuntu: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1970034 |
Let's add a botch since I've not made any progress with fixing the problem. Retry running a test twice if we hit the error 42 condition and are executing on CI. The CI variable is set by Semaphore: https://docs.semaphoreci.com/ci-cd-environment/environment-variables/#ci Updates cilium#598
Let's add a botch since I've not made any progress with fixing the problem. Retry running a test twice if we hit the error 42 condition and are executing on CI. The CI variable is set by Semaphore: https://docs.semaphoreci.com/ci-cd-environment/environment-variables/#ci Updates #598
The workaround works, so I'm closing this. |
Hi, What the workaround was? I am intrested, not getting my VM succesfully up and getting |
The workaround is to restart qemu a couple of times! Your error message looks different than ours though. |
We're having problems with our CI, where tests fairly often fail with exit code 42. That error is generated when the VM doesn't output anything and no success file is generated.
ebpf/run-tests.sh
Lines 60 to 62 in bf256fd
This happens across all of the packages we test and across multiple major kernel versions. It doesn't always reproduce, but usually rebuilding a PR once or twice will trigger the problem at least once.
The text was updated successfully, but these errors were encountered: