Skip to content

Conversation

@wrprice
Copy link
Contributor

@wrprice wrprice commented Oct 2, 2025

With the forkEvery=N option, not all Gradle test events go through the caseStart
path, meaning that a given session may not have a testSuite map within runningSuites
hence the NPE. The extra null check here (and probably also prior work from #8879) restores
the Test Results window functionality.

Was able to reproduce the original issue and verify this fixes #6000


^Add meaningful description above

Click to collapse/expand PR instructions

By opening a pull request you confirm that, unless explicitly stated otherwise, the changes -

  • are all your own work, and you have the right to contribute them.
  • are contributed solely under the terms and conditions of the Apache License 2.0 (see section 5 of the license for more information).

Please make sure (eg. git log) that all commits have a valid name and email address for you in the Author field.

If you're a first time contributor, see the Contributing guidelines for more information.

If you're a committer, please label the PR before pressing "Create pull request" so that the right test jobs can run.

PR approval and merge checklist:

  1. Was this PR correctly labeled, did the right tests run? When did they run?
  2. Is this PR squashed?
  3. Are author name / email address correct? Are co-authors correctly listed? Do the commit messages need updates?
  4. Does the PR title and description still fit after the Nth iteration? Is the description sufficient to appear in the release notes?

If this PR targets the delivery branch: don't merge. (full wiki article)

@mbien mbien added the Gradle [ci] enable "build tools" tests label Oct 2, 2025
@apache apache locked and limited conversation to collaborators Oct 2, 2025
@apache apache unlocked this conversation Oct 2, 2025
@mbien mbien added this to the NB28 milestone Oct 2, 2025
Copy link
Member

@mbien mbien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

makes sense to me, thanks for the fix!

@mbien mbien merged commit b32bab5 into apache:master Oct 2, 2025
32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Gradle [ci] enable "build tools" tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Empty test result window and a NullPointerException when running gradle test (junit 5) on a project with forkEvery = 1

2 participants