-
Notifications
You must be signed in to change notification settings - Fork 81
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
BazelCI failing for rules_haskell with release Bazel since Dec 19 #1470
Comments
Looking through the history it looks like the first instance of this failure occurs after merge of #1458. However, that PR seems unrelated to the issue. To be sure I started a pipeline with that commit reverted, but that fails as well. The first failing pipeline is here and the last succeeding one is here. So far, all bazel-CI runs since have consistently failed with this error. The docker image and bazel version between the two seems to be identical. The docker command and environment seem to be slightly different though I don't know if that's relevant.
Testing on a local build in bindist mode the file exists as expected
|
Anecdotally, I've seen the error @aherrmann mentions before in CI builds of a feature branch. It baffled me at the time because I couldn't see what caused it, and then it disappeared anyways. Hard to find now, because BuildKite doesn't offer a build log search feature AFAIK. |
Found a failing build: https://github.com/tweag/rules_haskell/runs/1677520752. This is from #1471. |
Looking at |
I'm as surprised as you that this wasn't an issue before, and it's unclear what changed to make this an issue now. But I'm also surprised that we get as far as not finding the |
Example buildkite failure:
https://buildkite.com/bazel/rules-haskell-haskell/builds/578#ec763d12-7c1e-4037-8ffb-b7937c361ce7
Unfortunately I don't have any insight into the error message.
Snip:
The text was updated successfully, but these errors were encountered: