-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Intermittent segmentation faults on Ubuntu 24.04 ARM, multiple Actions and binaries #11541
Comments
Hi @bbasata, Thank you for bringing this issue to our attention. We are looking into this issue and will update you on this issue after investigating. |
I am seeing flaky behavior on
Re-running the failing workflow will sometimes then run successfully. |
Does anyone have a simple repro for this I can use to investigate? |
You can fork https://github.com/cypress-io/cypress-docker-images and run the workflow https://github.com/cypress-io/cypress-docker-images/actions/workflows/example-tests.yml manually. The tests are randomly failing. Thanks for looking at this! I don't really want to disable |
See also the top post:
|
Description
Original report: hashicorp/setup-terraform#459
I'm investigating this report of segmentation faults on hashicorp/setup-terraform runs on ubuntu-24.04-arm. So I constructed a test repo that was reliably reproducing a ~15% fault rate.
In recent runs of the test repo, I am now seeing errors in actions/checkout (exit code 139) that were not occurring before. On the surface, exit code 139 matches Docker's exit code for a segmentation fault.
Runner image provisioner, for successful and failed runs: 2.0.422.1
The test repo:
GitHub repo (arm branch): bbasata/setup-terraform-issue-459:arm
Workflow runs: https://github.com/bbasata/setup-terraform-issue-459/actions/workflows/terraform.yml
Platforms affected
Runner images affected
Image version and build link
https://github.com/bbasata/setup-terraform-issue-459/actions/workflows/terraform.yml
Is it regression?
Yes
Expected behavior
Successful workflow runs
Actual behavior
Intermittent segmentation faults that fail the workflow run
Repro steps
arm
-- it runs 30 small jobsThe text was updated successfully, but these errors were encountered: