-
Notifications
You must be signed in to change notification settings - Fork 63
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 test int test #796
Cabal test int test #796
Conversation
I think this should be unblocked now with the merge of #840 |
@@ -20,3 +20,11 @@ cabal.project.freeze | |||
*~ | |||
*# | |||
.#* | |||
intTests/test_intro_examples/*.cnf |
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.
How did you determine what files from intTests
to put in .gitignore
?
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.
Chatted w/Ryan, this is in reference to #1067. @LisannaAtGalois , we could perhaps optimistically invoke a make clean after each target, ignoring failures (e.g. no clean target), but we should probably also make sure the gitignore us up-to-date with the latest test outputs.
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'll take a look and manually update the .gitignore (if needed). Maybe this could be automatically linted in CI by running all the tests (or their makefiles?) and checking to see if the git tree is dirty.
Invoking make clean at least on test success makes sense to me. Probably better to have failing tests not invoke that to preserve the output for post-mortem analysis.
This is now behaving functionally equivalently to the runtests.sh implementation - fixing the timeout to match what's currently used has all the results lining up now. The last thing this PR needs is to make the test details print on 100% success, and to remove runtests.sh. Follow-up work to smooth out how the integration tests are themselves specified to make it more cohesive with it being a cabal test target and PR-gating would be awesome:
|
Pending successful CI after merging in master, this should be ready to go in now. This does intersect a bit with #1111, which I will update after this is merged. |
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.
This looks great. Thanks!
Enables: cabal test integration_tests Co-authored-by: Kevin Quick <kquick@galois.com>
a01a232
to
3ccc0ee
Compare
Run intTests via a
cabal test
operation. Mirrors/replacesruntest.sh
functionality.