-
Notifications
You must be signed in to change notification settings - Fork 696
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
Track the exact source of ghc-*-options related warnings #5598
Track the exact source of ghc-*-options related warnings #5598
Conversation
c59b110
to
2b3f0cd
Compare
"url":"pull/5598", "account":"haskell", "repo":"cabal", "commit": "f055a5b0e51f6c68f449ad4b8247d95e93e6764f", "tag":"linux-7.10.3" }
"url":"pull/5598", "account":"haskell", "repo":"cabal", "commit": "f055a5b0e51f6c68f449ad4b8247d95e93e6764f", "tag":"linux-8.0.2" }
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, one quibble aside and pending Travis's thoughts. Thanks a bunch!
cabal-install/changelog
Outdated
@@ -2,6 +2,8 @@ | |||
|
|||
2.6.0.0 (current development version) | |||
* New solver flag: '--reject-unconstrained-dependencies'. (#2568) | |||
* 'check' reports warnings for various ghc-\*-options fields separately |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is affecting Cabal-the-library, the changelog note should go in Cabal/changelog
.
"url":"pull/5598", "account":"haskell", "repo":"cabal", "commit": "f055a5b0e51f6c68f449ad4b8247d95e93e6764f", "tag":"linux-7.6.3" }
Previously, when running `cabal check` all the various ghc-*-options flags were merged together, thus losing the information about the exact place of the warning. This PR implements separate checking of ghc-*-options, which allows us to give users more precise warnings. Fixes haskell#5342
2b3f0cd
to
3c1502b
Compare
"url":"pull/5598", "account":"haskell", "repo":"cabal", "commit": "f055a5b0e51f6c68f449ad4b8247d95e93e6764f", "tag":"osx-7.8.4" }
"url":"pull/5598", "account":"haskell", "repo":"cabal", "commit": "3c1502bb633b61ae4d24d40898fca66d7f169679", "tag":"linux-7.6.3" }
"url":"pull/5598", "account":"haskell", "repo":"cabal", "commit": "3c1502bb633b61ae4d24d40898fca66d7f169679", "tag":"linux-7.10.3" }
"url":"pull/5598", "account":"haskell", "repo":"cabal", "commit": "3c1502bb633b61ae4d24d40898fca66d7f169679", "tag":"linux-8.0.2" }
"url":"pull/5598", "account":"haskell", "repo":"cabal", "commit": "3c1502bb633b61ae4d24d40898fca66d7f169679", "tag":"linux-8.2.2" }
"url":"pull/5598", "account":"haskell", "repo":"cabal", "commit": "3c1502bb633b61ae4d24d40898fca66d7f169679", "tag":"linux-8.4.3" }
"url":"pull/5598", "account":"haskell", "repo":"cabal", "commit": "3c1502bb633b61ae4d24d40898fca66d7f169679", "tag":"osx-7.8.4" }
"url":"pull/5598", "account":"haskell", "repo":"cabal", "commit": "3c1502bb633b61ae4d24d40898fca66d7f169679", "tag":"linux-8.4.3-fdebug-expensive-assertions" }
"url":"pull/5598", "account":"haskell", "repo":"cabal", "commit": "3c1502bb633b61ae4d24d40898fca66d7f169679", "tag":"osx-8.0.2" }
Looks like one of the jobs failed by timeout, and another one got an error during dependency resolution. Both failures are unrelated to the changes in the PR. Is it okay to merge? |
I'd say to go for it. The solver error is happening on master, so it's not due to your code, and we bump right up against time limits on the OSX builders so it's inevitable that some builds get unlucky and time out. |
Merged, thanks! |
Previously, when running
cabal check
all the various ghc-*-options flags were merged together, thus losing the information about the exact place of the warning. This PR implements separate checking of ghc-*-options, which allows us to give users more precise warnings.Fixes #5342
Checklist:
[ci skip]
is used to avoid triggering the build bots.As for the testing approach, it is the same used for all other tests in the
Check
package.