Treat daemon startup timeout/error exceptions the same way as RMI errors
will result on regular retry cycle on them, hopefully eliminating or reducing appropriate exception reports
This commit is contained in:
+3
-2
@@ -319,6 +319,7 @@ object KotlinCompilerClient {
|
|||||||
catch (e: ConnectException) { null to e }
|
catch (e: ConnectException) { null to e }
|
||||||
catch (e: ConnectIOException) { null to e }
|
catch (e: ConnectIOException) { null to e }
|
||||||
catch (e: UnmarshalException) { null to e }
|
catch (e: UnmarshalException) { null to e }
|
||||||
|
catch (e: RuntimeException) { null to e }
|
||||||
|
|
||||||
if (res != null) return res
|
if (res != null) return res
|
||||||
|
|
||||||
@@ -420,9 +421,9 @@ object KotlinCompilerClient {
|
|||||||
if (daemonOptions.runFilesPath.isNotEmpty()) {
|
if (daemonOptions.runFilesPath.isNotEmpty()) {
|
||||||
val succeeded = isEchoRead.tryAcquire(daemonStartupTimeout, TimeUnit.MILLISECONDS)
|
val succeeded = isEchoRead.tryAcquire(daemonStartupTimeout, TimeUnit.MILLISECONDS)
|
||||||
if (!isProcessAlive(daemon))
|
if (!isProcessAlive(daemon))
|
||||||
throw Exception("Daemon terminated unexpectedly with error code: ${daemon.exitValue()}")
|
throw RuntimeException("Daemon terminated unexpectedly with error code: ${daemon.exitValue()}")
|
||||||
if (!succeeded)
|
if (!succeeded)
|
||||||
throw Exception("Unable to get response from daemon in $daemonStartupTimeout ms")
|
throw RuntimeException("Unable to get response from daemon in $daemonStartupTimeout ms")
|
||||||
}
|
}
|
||||||
else
|
else
|
||||||
// without startEcho defined waiting for max timeout
|
// without startEcho defined waiting for max timeout
|
||||||
|
|||||||
Reference in New Issue
Block a user