-
Notifications
You must be signed in to change notification settings - Fork 20
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
GitHub Actions #238
GitHub Actions #238
Conversation
1a0f61a
to
3b1e0ab
Compare
The cabal build succeeds, but the stack build doesn't. I need it to check the lower bounds. It fails with |
With lts-12.26, happy builds just fine. So if this only happens with lts-8.0, I can probably reproduce this locally?
Nope, succeeds. What's the difference between my laptop's environment and CI's? |
A later ticket, commercialhaskell/stack#5253 does mention that the same symptom keep reoccurring over and over again in a multitude of tickets. But that one specifically mentions lts-8, so that's probably the problem I am encountering. Unfortunately for me, that ticket is still open! While trying to reproduce the problem, however, the comments mention that if another version of |
Same result. |
Despite the fact that installing
|
Locally, installing
|
I'm trying to observe some more information about the build environment in CI, but all I get from e.g. |
All right, so |
Youhoo, it worked! |
This reverts commit 8a19e26.
|
Now the macOS build is failing. The logs seem to indicate that all the tests pass successfully and yet the executable exits with a non-zero error code:
But when we compare that output to a run which actually succeeds, we see that quite a few tests are missing!
So something happens between the |
This time we have a clearer error message, not sure why it was elided before:
I've actually encountered this locally earlier, and the solution I found online is simply to delete this |
Huh? but the build step worked just fine a moment ago, it was the test step which was failing, the build step was working fine! What's going on? |
looks like the file is not recognized as a macOS executable. Maybe it got corrupted somehow? |
skipping the cache worked, so I guess it did get corrupted. but I do want a cache, so that builds don't take so long. what if I simply create a new cache? |
seems to work! I don't know how the cache got corrupted in the first place, I just hope it doesn't happen again. |
Okay, those hardcoded |
Finally! |
Fixes #236. Probably. GitHub Actions always take several attempts...