-
Notifications
You must be signed in to change notification settings - Fork 134
Speedup version bump tests #445
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
Conversation
Dretch
left a comment
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.
Looks good to me.
|
|
||
| spago ["bump-version", "minor"] >>= shouldBeSuccess | ||
| getHighestTag >>= (`shouldBe` Just "v1.2.3") | ||
| -- TODO should this work or should we strip these in parser implementation? |
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.
PREREL / META should probably be allowed - for one thing because there are existing packages that have such versions - e.g. halogen v5.0.0-rc.7.
| parseVersionBump "1.2.3" `shouldBe` Just (Exact (SemVer 1 2 3 [] [])) | ||
|
|
||
| before_ (initGitTag "v1.2.3") $ it "Spago should not make a tag when not passing --no-dry-run" $ do | ||
| -- TODO is this desired behavior, or should we just drop ONE 'v'? I'd agree it's edge case, but still :-) |
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.
I don't know. 🤷♂️
|
@f-f just wanted to check with you what's the general strategy around PR reviews. Should I wait for your review/approval before I merge, or is just one review enough, like in the case of this PR? |
|
@jhrcek great point, thanks for asking. This has not come up before so that's why we don't have a written policy about it yet I think a review from a contributor is enough to merge, no need to wait for my review :) |
|
@jhrcek thanks for doing this 🙂 |
Description of the change
Attempt to speed up test suite by focusing on the slowest tests as described in #440
Locally this change seems to have shaved off ~20s of test running time.
Checklist:
README