Closed igor-rubis closed 11 months ago
This looks like a general problem with Gradle that would happen even without the test retry plugin. You seem to be passing some kind of debug options to the JVM. Are you running this with --debug-jvm
?
With --debug and --stacktrace
Well, as I said. For the first time it a test is executed like it should in Gradle Test Executor 1
.
But if I add the retry
plugin, I see the following in the output:
2023-10-06T18:28:15.902+0100 [INFO] [org.gradle.process.internal.DefaultExecHandle] Starting process 'Gradle Test Executor 2'. Working directory: ~/project
2023-10-06T18:28:15.902+0100 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTING
2023-10-06T18:28:15.902+0100 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Waiting until process started: Gradle Test Executor 2.
2023-10-06T18:28:15.916+0100 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTED
2023-10-06T18:28:15.917+0100 [INFO] [org.gradle.process.internal.DefaultExecHandle] Successfully started process 'Gradle Test Executor 2'
2023-10-06T18:28:15.917+0100 [DEBUG] [org.gradle.process.internal.ExecHandleRunner] waiting until streams are handled...
2023-10-06T18:28:16.181+0100 [ERROR] [system.err] ERROR: transport error 202: connect failed: Connection refused
2023-10-06T18:28:16.181+0100 [ERROR] [system.err] ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
2023-10-06T18:28:16.181+0100 [ERROR] [system.err] JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugInit.c:750]
2023-10-06T18:28:16.183+0100 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: FAILED
2023-10-06T18:28:16.183+0100 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Process 'Gradle Test Executor 2' finished with exit value 2 (state: FAILED)
2023-10-06T18:28:16.184+0100 [DEBUG] [org.gradle.internal.work.DefaultWorkerLeaseService] Worker lease root.1.91.212 completed (1 worker(s) in use)
2023-10-06T18:28:16.184+0100 [DEBUG] [org.gradle.internal.resources.AbstractTrackedResourceLock] Dispatch org.gradle.api.internal.tasks.testing.processors.RestartEveryNTestClassProcessor@2a1c6905: released lock on root.1.91.212
This happens during the retry process.
Are you passing any debug options as JVM args, like -agentlib:jdwp=...
?
You were right, it was an issue with Intelij running the task.
I'm using the plugin for the first time, so might be missing something, but anyways. Related code in my
build.gradle
:I created a sample test using groovy:
With
--debug
and--stacktrace
after the test fails for the first time, I see the following output in the console:And as a result the test doesn't get retried.