-
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
testsuite: Refactor withShorterPathForNewBuildStore #9505
Conversation
8ff6d70
to
fb56227
Compare
Can someone review this please? |
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
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.
Thank you.
@mpickering: ready for the label! |
This needs rebasing as some tests are updated to use the old API. |
fb56227
to
f78b707
Compare
f78b707
to
c906452
Compare
I've rebased this commit (basically cherry-picked from the private dependencies branch where it was already updated) |
0e6593c
to
ebbd10f
Compare
0932a33
to
555e791
Compare
@alt-romes: I'm afraid you've lost the race with mergify (and possibly other PR authors). Could you resolve the conflicts one last time and I'd try to prod mergify until it yields? |
This makes `withShorterPathForNewBuildStore` fit more nicely into the rest of the testing infrastructure. * Move `withShorterPathForNewBuildStore` to `TestM` monad * Move responsibility for passing `--store-dir` to `cabalGArgs` function * Move `findDependencyInStore` into `TestM`, and remove requirement to pass path to store directory. * Introduce `testStoreDir` function which returns the store location (and honours `withShorterPathForNewBuildStore`) * Migrate tests which use `withShorterPathForNewBuildStore`.
555e791
to
2a2d0b3
Compare
@alt-romes: thanks a lot! The merge label is already there and since the PR has been blocked on a merge conflict for so long, I think we can manually set |
@mergify regresh |
❌ Sorry but I didn't understand the command. Please consult the commands documentation 📚. |
@mergify refresh |
✅ Pull request refreshed |
@mergify queue |
🛑 This
|
Mergify got confused. It seems to think that -mergify-configuration-changed and that there's not enough reviews. I may end up merging manually. |
@mergify unqueue |
✅ The pull request is not waiting to be queued anymore. |
@mergify queue |
🛑 The pull request has been merged manuallyThe pull request has been merged manually at 774ff04 |
@mergify rebase |
☑️ Nothing to do
|
@mergify backport 3.12 |
✅ Backports have been created
|
…10059) * testsuite: Refactor withShorterPathForNewBuildStore This makes `withShorterPathForNewBuildStore` fit more nicely into the rest of the testing infrastructure. * Move `withShorterPathForNewBuildStore` to `TestM` monad * Move responsibility for passing `--store-dir` to `cabalGArgs` function * Move `findDependencyInStore` into `TestM`, and remove requirement to pass path to store directory. * Introduce `testStoreDir` function which returns the store location (and honours `withShorterPathForNewBuildStore`) * Migrate tests which use `withShorterPathForNewBuildStore`. (cherry picked from commit 2a2d0b3) # Conflicts: # Cabal-tests/Cabal-tests.cabal # Cabal-tests/lib/Test/Utils/TempTestDir.hs * !fixup resolve conflicts * fixup! always import `(</>)` --------- Co-authored-by: Matthew Pickering <[email protected]> Co-authored-by: Artem Pelenitsyn <[email protected]> Co-authored-by: brandon s allbery kf8nh <[email protected]>
This makes
withShorterPathForNewBuildStore
fit more nicely into the rest of the testing infrastructure.withShorterPathForNewBuildStore
toTestM
monad--store-dir
tocabalGArgs
functionfindDependencyInStore
intoTestM
, and remove requirement to pass path to store directory.testStoreDir
function which returns the store location (and honourswithShorterPathForNewBuildStore
)withShorterPathForNewBuildStore
.Please read Github PR Conventions and then fill in one of these two templates.