-
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
cabal check complains about -Werror in cabal.project #8490
Comments
I am trying to reproduce this on my machine but cannot, the way to trigget is is with:
in edit: fixed cabal.project |
See https://github.com/nomeata/haskell-rec-def/actions/runs/3105946791/jobs/5032197241#step:21:29 for a failing run. It uses
so yes, that should be it. (The -Wall is part of the cabal file, if that makes a difference) |
Can you try to unpack and then edit: wait, I see an “unguarded” (not under flag) Did CI fail with that? |
🤦🏻 Sorry! My brain was thinking “I should add -Werror wait I should only add it to CI” and my fingers must have added it to the .cabal file before I noticed. |
No worries, this highlights `cabal check` could benefit for specific column:row indication for warnings.
Il 22 settembre 2022 alle 10:20 Joachim Breitner ha scritto:
… 🤦🏻
Sorry! My brain was thinking “I should add -Werror wait I should only add it to CI” and my fingers must have added it to the .cabal file before I noticed.
--
Reply to this email directly or view it on GitHub:
#8490 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
Describe the bug
cabal check
complains about-Werror
even if it is set in thecabal.project
fileExpected behavior
Given that
-Werror
is only bad if it is part of the.cabal
file uploaded to Hackage, setting it in thecabal.project
file should not trigger the bug.System information
This is
cabal-3.6.2.0
from ghcup viahaskell-ci
.Additional context
In my case the
cabal.project
is created byhaskell-ci
when usingwhich I tought might be a good way to get
-Werror
active on CI without affecting the Hackage releases.(This is a minor thing of course, but still worth noting down.)
The text was updated successfully, but these errors were encountered: