-
Notifications
You must be signed in to change notification settings - Fork 524
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
Tracking: transient CI failures #1095
Comments
That's not the actual error. The actual error is grub failing to build due to the build container dying(?):
|
Heheh... sadly, neither is "no such container" or "no such image", which just mean that the grub build failed and so there was no output, and "failed to run custom build command" just means we need to look for a real error above. Sadly, it looks like the check logs were lost when they were rerun. |
CI runner ran into a random segfault during unit tests:
Full log:
|
Sometimes Github Actions fails to connect to CI runners
|
Ran into this 4-5 times:
|
Intermittent CI failure that seems to only happen for aws-k8s-1.16/aarch64. Potential race?
https://github.com/bottlerocket-os/bottlerocket/pull/1317/checks?check_run_id=1881507065 |
This issue has mostly been fixed by the merged PRs linked above. Let's re-open this when CI ever starts failing again. |
This is a place to track CI failures that were not caused by code issues but by a transient issue in the CI runner.
Known issues:
failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: unexpected status code https://registry-1.docker.io/v2/docker/dockerfile/manifests/1.1.3-experimental: 500 Server Error
failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: rpc error: code = Unknown desc = failed to build LLB: mount already exists with name
The text was updated successfully, but these errors were encountered: