Add simple workflow to run test from verbose.tests#436
Draft
jeff5 wants to merge 3 commits into
Draft
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 existing workflow for Java 17 and 25 compatibility uses an Ant target that runs the regrtest normally, then re-runs the failed tests in verbose mode, so we can see exactly which tests fail and the cause. When it comes to networking tests, this is unsatisfactory if they fail to close their sockets, which they frequently do on failure, since the verbose run then fails comprehensively because the sockets are busy, not for the original cause.
This workflow allows us to specify which tests to run verbose, so that we may run just the ones that caused trouble.