-
Notifications
You must be signed in to change notification settings - Fork 221
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
Autobuild: Mac legacy CI failure: hdiutil: create failed - No child processes #3207
Comments
Some first hints:
All in all, I believe the reason is outside of code and dependencies which are managed in our git.
Not the reason:
Things to try/rule out:
|
After a huge amount of debugging, I come to the conclusion that the issue stems from CodeQL which seems to cause problems in a helper program which is called by hdiutil (
I'm going to prepare a workaround PR for Jamulus tomorrow, will report my findings to the other issues around this topic and will file a bug report with CodeQL. IMO there must be an easy way to get rid of CodeQL selectively (e.g. using environment variables), but I haven't found such a way in docs or in the dylib itself. We might want to re-consider whether running CodeQL on ordinary builds is such a good idea. |
Work around did its job: https://github.com/hoffie/jamulus/actions/runs/7188809801/job/19579191939 |
This uses CodeQL v2.14.6.
This uses CodeQL v2.15.0. https://github.com/github/codeql-action/blob/main/CHANGELOG.md#2222---12-oct-2023 |
I've been working on this every now and then and can prove that CodeQL changes the behavior of hdiutil. https://github.com/hoffie/codeql-hdiutil-breakage/actions |
My test cases no longer reproduce the issue. CI on github/codeql-action#2016 |
I agree. I found this issue independently just this week, and found disabling CodeQL fixed it. I'm not sure what the usefulness is of having CodeQL run every time on almost every platform. I suppose it catches platform-specific code? |
Strangely, as of today, without any changes in that area, the Mac Legacy build has started working again. See https://github.com/jamulussoftware/jamulus/actions/runs/7506943410 and https://github.com/softins/jamulus/actions/runs/7505799220 |
And then it stopped working again. I think this commit dbe7286 should be raised as a PR sooner rather than later. It helped the Mac Legacy build run properly for some test builds on my fork, and did not upset the main Mac build either. I am happy to raise the PR myself if it helps - I have cherry-picked the above commit into a branch of my own, and that carries the original author attribution over. |
Having added this to my branch, I then moved the CodeQL from the Legacy build back to the Main build. It completed without error: https://github.com/softins/jamulus/actions/runs/7699409889 |
Describe the bug
CI Mac Legacy regularly fails with this error:
To Reproduce
Run CI
Expected behavior
Clean build
Screenshots
Operating system
Mac legacy
Version of Jamulus
git
Additional context
The text was updated successfully, but these errors were encountered: