Failed to start remote test generation service

Issues
#1

Hi everyone, I was just trying to execute diffblue but he failed to start.

He gave me this error : Failed to start remote test generation service.

DiffBlue intelliJ plugin version 2020.12.02-eval.2020.2.1

JDK version 1.8 (1.8_261)

Here is the log :

15:13:36.215 [INFO][pool-6-thread-1][c.d.i.p.ui.a] Commencing test creation - Analyzing 6 methods in total
15:13:36.225 [INFO][pool-6-thread-1][c.d.i.p.ui.a] Logfile location - C:\Users\sebas\AppData\Local\Temp\diffblue\log\cover-plugin.log
15:18:50.795 [WARN][ApplicationImpl pooled thread 8][c.d.i.p.ui.a] Failed to start remote test generation service - Please submit an error report with a detailed description of what you were doing before the error
com.diffblue.cover.api.k: Failed to start remote test generation service
at com.diffblue.cover.generation.phaser.InvokeDriver.invoke(SourceFile:169)
at com.diffblue.cover.api.g.b(SourceFile:1294)
at com.diffblue.intellij.plugin.actions.a.run(SourceFile:342)
at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:935)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcessWithProgressAsync$5(CoreProgressManager.java:442)
at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$3(ProgressRunner.java:235)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:170)
at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:629)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:581)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:60)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:157)
at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$4(ProgressRunner.java:235)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:668)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:665)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:665)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: com.diffblue.cover.service.g: Failed to connect to the analyzer service. Service not responding.
at com.diffblue.cover.service.c.d(SourceFile:343)
at com.diffblue.cover.service.c.a(SourceFile:175)
at com.diffblue.cover.api.b.b.a(SourceFile:159)
at com.diffblue.cover.api.b.f.a(SourceFile:79)
at com.diffblue.cover.generation.phaser.InvokeDriver.a(SourceFile:147)
at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
… 1 common frames omitted

Thank you in advance for your help

Sébastien

#2

Hi Sébastien,

Thanks for getting in touch - you have certainly stumbled across something unfortunate here

May I ask what version of IntelliJ you are using?

Thanks again, we will get this sorted for you ASAP

Matt @ Diffblue

#3

Hi Matt, thanks for your support.

I use IntelliJ Ultimate edition 2020.2.4

Sebastien

#4

Hi Sébastien,

Many thanks for reporting that log, that is very helpful. There is also another log file which might contain useful information, known as the ‘cover-server.log’ which should be in this location for you:
C:\Users\sebas\AppData\Local\Temp\diffblue\log\cover-server.log Could show us the content of that log file? Do you run any kind of firewall on your system that blocks IP connections on the loopback addresses (127.0.0.1 for IPv4 or ::1 for IPv6) ? Or any other system policy settings that might do that?

Hopefully with that information we should be able to resolve this for you,
Chris.

#5

Hi Chris, thanks for your help,

here is the log of cover-server :
15:13:39.057 [INFO][main][c.d.c.s.a.a.b] Starting new remote monitor client

I have windows defender and bitdefender antivirus

I turn them off but i get the same result.

I also tried to restore the hosts file but it still doesn’t work

Seb

#6

Thanks for the extra log information Sébastien. We have not yet been able to reproduce this problem at our end yet, so we are going to add some additional detailed logging into the next release (which will be version 2021.01.01) . We’d be really grateful if you could test it again once it is released!

#7

Thanks for your reply Chris, I would be happy to use it.
Do you have a planned date for this release?

#8

Thanks Seb, this would be greatly appreciated

The release is due to be out on Wednesday (we generally release every 2 weeks) - we will post here when it has gone live on the JetBrains AppStore

Thank you once again for your help, as I am sure you are aware these sorts of issues are mega important for us to fix but also mega hard to track down, your help is really appreciated here

Chris or I will be in touch soon

Thanks

Matthew
Head of Product @ Diffblue

#9

Hi everyone,

I update my plugin and I always have the same issue

Here my cover-plugin.log :

17:59:02.716 [INFO][ApplicationImpl pooled thread 19][c.d.i.store.f] Converting index to a supported format and re-indexing; this may take some time.
17:59:09.530 [INFO][ApplicationImpl pooled thread 11][c.d.i.store.f] Converting index to a supported format and re-indexing; this may take some time.
18:10:56.011 [INFO][pool-10-thread-1][c.d.c.api.b.b]
18:10:56.011 [INFO][pool-10-thread-1][c.d.c.api.b.b] Creating tests:
18:10:56.011 [INFO][pool-10-thread-1][c.d.c.api.b.b] ---------------
18:10:56.026 [INFO][pool-10-thread-1][c.d.i.p.ui.a] Commencing test creation - Analyzing 3 methods in total
18:10:56.066 [INFO][pool-10-thread-1][c.d.i.p.ui.a] Logfile location - C:\Users\sebas\AppData\Local\Temp\diffblue\log\cover-plugin.log
18:16:23.909 [WARN][ApplicationImpl pooled thread 41][c.d.i.p.ui.a] Failed to start remote test generation service - Please submit an error report with a detailed description of what you were doing before the error
com.diffblue.cover.api.l: Failed to start remote test generation service
at com.diffblue.cover.generation.phaser.InvokeDriver.invoke(SourceFile:169)
at com.diffblue.cover.api.h.b(SourceFile:1294)
at com.diffblue.intellij.plugin.actions.a.run(SourceFile:343)
at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:962)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcessWithProgressAsync$5(CoreProgressManager.java:472)
at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$3(ProgressRunner.java:235)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:178)
at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:658)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:610)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:65)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:165)
at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$4(ProgressRunner.java:235)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:668)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:665)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:665)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: com.diffblue.cover.service.g: Failed to connect to the analyzer service. Service not responding.
at com.diffblue.cover.service.c.d(SourceFile:343)
at com.diffblue.cover.service.c.a(SourceFile:175)
at com.diffblue.cover.api.b.b.a(SourceFile:159)
at com.diffblue.cover.api.b.e.a(SourceFile:97)
at com.diffblue.cover.generation.phaser.InvokeDriver.a(SourceFile:147)
at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
… 1 common frames omitted

And my cover-server.log :

18:10:59.440 [INFO][main][c.d.c.s.a.a.b] Starting new remote monitor client

Thank you for your help

#10

Many thanks for trying this out Sébastien - I’ve sent you a Private Message so that we can try some additional diagnostics. We really appreciate your patience and engagement on this issue because we’d love to get to the bottom of this.

Thanks again,
Chris

#11

Hi Sébastien - thanks for the extra logs you sent me via email. We are still working to track this down, but we have some clues now. In your private communications you mentioned that the Diffblue Cover was working for you on one of your computers, but not this particular computer. Out of interest, is this computer where it does not work slower, or more heavily loaded with tasks than the computer where it does work?

Many thanks for all you help with this - we really appreciate the feedback!
Chris

#12

Hi Sébastien,

Thanks to the information you’ve provided we’ve been able to find a few places where we may have been too aggressive with some timeouts and have now made some adjustments. These adjustments will be incorporated into our next release, 2021.02.01, which is scheduled for release in the first week of February. Once that release is available, could you please upgrade and try again?

Many thanks,
Chris.