Quarkus test invocations listed as "phantom" builds via GH Gradle build action?

[snazy]

Describe the bug

(This is rather a heads-up than a bug report)

We're using Gradle to build and test our code built for Quarkus and use Gradle's Github action to run Gradle, which is a nice way to use Gradle in GH actions. That action generates a build summary w/ all Gradle invocations, the requested tasks (aka command line arguments) and the outcome of the build.
But it also lists some "phantom" Gradle builds that request the classes task - the issue is: our build does not start and Gradle build explicitly asking to run classes - and definitely not that often. I've attached a screenshot to the related issue on the gradle-build-action project: gradle/actions#28

Expected behavior

No "phantom" classes builds (listed)

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @glefloch, @quarkusio/devtools

[geoand]

Is this still a problem with your latest Gradle changes?

[snazy]

Ah, it was a problem in the GH action. Nothing to do w/ Quarkus

[geoand]

Thanks for the update