-
Notifications
You must be signed in to change notification settings - Fork 50
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
tests seem to hang on Mac on GitHub Actions #79
Comments
@mvdan Just to clarify, we haven't ruled out an issue on our end but the problem here seems to be something is holding on to the runner for the full 6 hours at which time the service times it out. We'll continue digging on the service side but if you can help us by confirming on the workflow side that nothing is keeping the agent process busy, that would be great. Please let us know what you find and I'll update here as soon as we know more. Thanks! |
Thanks! The PR #77 seems to make the hang far more likely, because it makes some of the heavier tests run in parallel. I'm going to push some extra stuff in that PR to try to see what's happening when it hangs. |
We never found out the "why", but I assume it has something to do with all the concurrent builds that get triggered, which honestly aren't a great idea to begin with. For some reason, a bunch of In any case, though, the fact that |
There's an underlying bug (or set of them) here that is causing problems on macos. A temporary fix to get macos into CI is to disable the parallelism but we really need to find the real cause and fix that. Ref: #79
There's an underlying bug (or set of them) here that is causing problems on macos. A temporary fix to get macos into CI is to disable the parallelism but we really need to find the real cause and fix that. Ref: #79
There's an underlying bug (or set of them) here that is causing problems on macos. A temporary fix to get macos into CI is to disable the parallelism but we really need to find the real cause and fix that. Ref: #79
There's an underlying bug (or set of them) here that is causing problems on macos. A temporary fix to get macos into CI is to disable the parallelism but we really need to find the real cause and fix that. Ref: #79
Going to close this since #400 is merged to deal with the consequences of this problem, although not really the cause - there's TODOs in the code now to point to it. |
There's an underlying bug (or set of them) here that is causing problems on macos. A temporary fix to get macos into CI is to disable the parallelism but we really need to find the real cause and fix that. Ref: #79
For example: https://github.com/ipld/go-ipld-prime/pull/77/checks?check_run_id=1083075042
This seems to happen rather frequently; we've seen six of these in just a week, where twenty or so workflows were run.
GitHub confirmed this doesn't seem like a bug on their end, because the process is still running. But how can that be, since a test package execution should timeout after ten minutes by default? I'm pretty sure that's enforced via kill signals, too.
I'm opening this issue to investigate.
The text was updated successfully, but these errors were encountered: