-
Notifications
You must be signed in to change notification settings - Fork 161
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
Sporadic failure to build IO in the macOS CI job #4374
Comments
It actually seems to be very frequent, indeed I haven't managed to get this job to pass on #4372 for quite a while now. I'll also note that GAP is compiled without
(that's of course an example of a build where IO did actually compile). |
This is caused by the fact that autoconf recently was update to 2.71 (after years of no activity at all), and apparently they decided it's a good idea to suddenly deprecate a ton of stuff. And homebrew now ships it. The fact that it only hits us sometimes likely is due to difference in the various macOS VMs used by GitHub; I assume the issue will happen more and more often... I can work on a fix for io, but it is likely that similar issues will affect more packages... |
Ah, thank you for diagnosing this @fingolfin. Temporarily, we could remove the code coverage from the Mac build - we would lose coverage data for Mac-specific code, but (if such a job doesn’t already exist) we could replicate the rest of the coverage in another Ubuntu job. That would stop IO from needing to be built. What do you think? |
I tried temporarily fixing this based on https://bugs.ruby-lang.org/issues/17723 ( which said run autoreconf -f -i). That actually seemed to fix it on my machine -- still lots of warnings, but at least it built. In https://github.com/ChrisJefferson/gap/tree/fix-autoconf271 (only change is in BuildPackages.sh, where I add:
|
Currently the macOS job is failing because IO is not building, which is requiring by the code coverage system, and this causes the job to fail. See: gap-system#4374 By adding NO_COVERAGE=1 to this job, IO will no longer need to be compiled. Obviously, in the long term we want coverage on this job, and we want to be able to compile IO, but this will get the CI running for the rest of GAP in a non-controversial way in the meantime, I hope.
I believe this issue has been resolved by my changes to |
I first mentioned this #4372 (comment) and #4373 (comment).
Starting recently (I first noticed it today, I've seen it about four times so far) the
Gather coverage data
step sometimes fails in the macOS job (docomp testinstall - BOOTSTRAP_MINIMAL=yes - macos-latest
), because it cannot load the profiling package. @ChrisJefferson has looked a little further and noticed that this is becauseIO
fails to build. From #4373 (comment):Failure instances:
The text was updated successfully, but these errors were encountered: