Run.dev.tests JUnit task with fork enabled to prevent hanging #485
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fentonreid
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The JUnit task for run.dev.tests in defects4j.build.xml has the fork attribute enabled, with fork mode set to 'once' to create a single JVM for all tests. A default timeout of 3 minutes is also specified, to stop the execution of all tests after this period.
This change allows for endless execution of relevant tests for the defects4j 'test' command with the -r flag. Without the run.dev.tests task hanging indefinitely, a problem encountered in Dockerized defects4J.