-
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
Add tests for project imports and constraint version conflicts #9680
Conversation
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.
You have a number of files without final newlines again.
Thanks @geekosaur, fixed now. |
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.
Excellent. Particular thanks for the documentation of the tests.
- Allow for bad behaviour of master branch - Add cyclical checks with same file names and hops - Add cyclical import tests with 1 and 2 hops in cycle - Expected output has project with full project path - Add newlines at EOF
86d66cb
to
78fcdc6
Compare
Label merge+no rebase is necessary when the pull request is from an organisation. |
Ooops, I forgot to rebase, didn't I? |
I rebased today didn't I? |
Apparently somebody merged between then and our merge, but the git history complication is marginal this time. |
While reviewing #9578, I saw opportunity for more project import tests in addition to those added in #9665. This also adds tests of constraint version priority capturing the current behaviour.
I've left comments in
cabal-testsuite/PackageTests/ConditionalAndImport/cabal.test.hs
where the current behaviour is not good.