-
Notifications
You must be signed in to change notification settings - Fork 19
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
NetBSD sometimes gets EPIPE errors #21
Comments
Update: NetBSD has been breaking consistently the past few builds, so something's up. |
Could you please re-run the job with debug logging enabled [1]? [1] https://github.blog/changelog/2022-05-24-github-actions-re-run-jobs-with-debug-logging/ |
Looks like the second run worked, so it's back to being intermittent. https://github.com/Slackadays/Clipboard/actions/runs/4040118288/jobs/6955765382 |
Could you try and run with debug info enabled for a while and report back here when it doesn't work? |
I've added the right debug variable under Update: It hangs after showing these steps:
Now failing: https://github.com/Slackadays/Clipboard/actions/runs/4047572932/jobs/6962013350 Now spinning its wheels again |
I've seen this issue before. The problem seems to be that the action doesn't terminate even the when command has failed, or GitHub Action doesn't pick up that the action has failed and just continue running. Both [1] and [2] are legitimate failures (make is failing). I tried this as well with FreeBSD, failing a build on purpose [3]. You can see on line 621 that the SSH process failed. That's the process that's executing the command inside the VM. That's supposed to fail when the command inside the VM fails. But the action continues running (for some reason) and gets cancelled on line 632 by the GitHub Action timeout. [1] finally timed out after the default 6 hours. You can now see the failing error. Unfortunately you need to wait for the timeout to see the output, unless you look at it from the start. For now, as a workaround, I recommend setting a timeout [5]. Based on [4], I suggest a timeout of 20 minutes. [1] https://github.com/Slackadays/Clipboard/actions/runs/4045627902/jobs/6957357468 |
@Slackadays can you try this commit and see if it works better: cc6f408. I think you can point to a commit without me having to make a proper release. |
This one's actually failing earlier now, so it looks like your change could have fixed the issue. https://github.com/Slackadays/Clipboard/actions/runs/4057206961/jobs/6982674945 |
Every few runs or so, the Clipboard NetBSD action gets an EPIPE error at
Promise
. This only happens with NetBSD and doesn't seem to follow any pattern other than being intermittent. However, a re-run has always fixed the problem so far. See https://github.com/Slackadays/Clipboard/actions/runs/4040118288/jobs/6945480282#step:3:66I hope this bug is fixable because I still think CPA is a genius idea 🥇
The text was updated successfully, but these errors were encountered: