Skip to content

Conversation

tresat
Copy link
Member

@tresat tresat commented Sep 9, 2025

In older JUnit 4 versions, the Runner retrieved from a Request was not the same instance across multiple invocations, so we can't rely on this behavior. Instead create our own request after we finish applying filters to the initial Runner.

In older JUnit 4 versions, the Runner retrieved from a Request was not the same instance across multiple invocations, so we can't rely on this behavior.  Instead create our own request after we finish applying filters to the initial Runner.
@tresat
Copy link
Member Author

tresat commented Sep 9, 2025

@bot-gradle test this

@bot-gradle

This comment has been minimized.

@tresat
Copy link
Member Author

tresat commented Sep 9, 2025

@bot-gradle test this

@bot-gradle

This comment has been minimized.

@bot-gradle
Copy link
Collaborator

The following builds have been cancelled:

@tresat tresat self-assigned this Sep 9, 2025
@tresat tresat added in:testing in:testing-junit4 a:chore Minor issue without significant impact labels Sep 9, 2025
@tresat tresat added this to the 9.2.0 RC1 milestone Sep 9, 2025
@bot-gradle
Copy link
Collaborator

The following builds have passed:

@tresat tresat marked this pull request as ready for review September 9, 2025 15:35
@tresat tresat requested review from a team as code owners September 9, 2025 15:35
@tresat tresat requested a review from big-guy September 9, 2025 17:40
@tresat tresat added this pull request to the merge queue Sep 9, 2025
Merged via the queue into master with commit 0d39112 Sep 9, 2025
33 checks passed
@tresat tresat deleted the tt/92/support-junit4.0-requests branch September 9, 2025 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:chore Minor issue without significant impact in:testing in:testing-junit4
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants