Running unit test in UI causes, "Click to run tests" to disappear on newer versions of gradle

[sbs20]

Environment:

• VS Code Version: 1.104.1
• Extension Version: 0.30.2
• JDK Type & Version: Adoptium 21.0.5.11
• OS Type & Version: Windows 11 24H2

Step to Reproduce:

• Medium sized, multi-module java project with Gradle 8.14.3. 19 sub modules.
• Run a JUnit5 unit test in the UI by clicking "Click to run tests" icon (next to the unit test in the UI)

Expected Behavior:

• After test completion, I expect to be able to press "Click to run tests" again immediately

Actual Behavior:

• "Click to run tests" icon (next to the unit test in the UI) disappears - as in, this one:

  

• "Build Server for Gradle" output console just shows and scrolls this sort of thing for about 5-10 minutes while it seemingly rebuilds

  [INFO - 12:17:47] Sending response 'workspace/buildTargets'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'workspace/buildTargets'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'buildTarget/outputPaths'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'buildTarget/sources'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'buildTarget/resources'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'buildTarget/outputPaths'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'buildTarget/sources'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'buildTarget/resources'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'buildTarget/dependencyModules'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'buildTarget/dependencyModules'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'buildTarget/javacOptions'. Processing request took 2 ms.
  [INFO - 12:17:48] Sending response 'workspace/buildTargets'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'workspace/buildTargets'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'buildTarget/outputPaths'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'buildTarget/sources'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'buildTarget/resources'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'buildTarget/outputPaths'. Processing request took 0 ms.
  [INFO - 12:17:48] Sending response 'buildTarget/sources'. Processing request took 0 ms.
  

• Eventually (10 mins later?) "Click to run tests" icon reappears.

Related Issues:

None found

Further diagnostic info

• Happens on Java Adoptium 17.0.6.10 & 21.0.5.11
• Also happens with Gradle 9.0.0
• Most importantly it does not happen if I downgrade Gradle (in gradle/wrapper/gradle-wrapper.properyes) to 8.11.1. This is my current workaround.
• I have not dug further to work out where, between 8.11.1 and 8.14.3 it all goes wrong

Total speculation

• My guess is that this is a combination of a moderately large project in conjunction with using build-server-for-gradle and a newish version of Gradle.
• I'd further speculate that Gradle itself has changed and creates (or detects?) some output when a unit test has run which maybe invalidates it cache or something.

[github-actions]

Hi @sbs20, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Suggestions

• Workaround: Pin your Gradle wrapper to 8.11.1 (in gradle/wrapper/gradle-wrapper.properties) to avoid the rebuild loop and restore the run-test gutter icon immediately.

• Gather diagnostics:

  • In your VS Code settings, enable verbose tracing for the Java language server:

    "java.trace.server": "verbose"

  • Reproduce the issue and collect the Java Language Server and Build Server for Gradle output channels.

• File a bug if this reproduces consistently on Gradle ≥ 8.12:

  • Create a new issue at https://github.com/redhat-developer/vscode-java/issues/new
  • Include your VS Code version, extension versions, OS, JDK, Gradle version, your gradle-wrapper.properties, test project, and the collected logs.

No duplicates or high-confidence references found.

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!

[seancynnaelera30-cell]

All wright