-
Notifications
You must be signed in to change notification settings - Fork 701
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
Unnecesarry rebuild with new-build #3317
Comments
Is Cabal's exit code really non-zero? (Check with (FWIW I'm trying to reproduce locally, but it's a lot of packages to build haha.) |
|
Is the |
No the --dry-run isn't necessary there, but it means it'll stop after giving us the relevant info. |
Sorry for not replying, for some reason I didn’t get the notification mails for this issue. Cabals exit code is zero. Here are the logs for monad-logger and bifunctors. Both fail to build (which is probably because we don’t have bounds because we relied on stackage so far). I’ll leave this issue open since not printing anything (without verbose) and exiting with 0 is at least a usability problem. |
Ahh ok, so this is not actually a rebuild but it's the issue about reporting failed builds. We recently merged a patch to report the non-0 exit code in this situation but reporting a detailed error message in this situation is still TODO. |
Ok, I'll close in favour of #3394 which tracks this issue. |
I was trying out the new-build using bafbbc6 on the cabal 1.24 branch, but I’m experiencing some weird rebuilds.
The repo I used was haskell-ide-engine with a cabal.project file.
The build doesn’t error but it also doesn’t seem to build the main executable and everytime I restart it, it builds
monad-logger
andbifunctors
again.Here’s the output of
cabal new-build -v
of one of those rebuildsThe text was updated successfully, but these errors were encountered: