Fix sluggish elapsed time when no build output, fixes #224

This commit is contained in:
Guillaume Nodet
2020-11-16 10:11:41 +01:00
parent 668d4e4526
commit cf5c512652

View File

@@ -121,12 +121,12 @@ public enum Environment {
* Time after which a daemon will send a keep-alive message to the client if the current build * Time after which a daemon will send a keep-alive message to the client if the current build
* has produced no output. * has produced no output.
*/ */
MVND_KEEP_ALIVE("mvnd.keepAlive", null, "1 sec", true), MVND_KEEP_ALIVE("mvnd.keepAlive", null, "100 ms", true),
/** /**
* The maximum number of keep alive message that can be lost before the client considers the daemon * The maximum number of keep alive message that can be lost before the client considers the daemon
* as having had a failure. * as having had a failure.
*/ */
MVND_MAX_LOST_KEEP_ALIVE("mvnd.maxLostKeepAlive", null, 3, false), MVND_MAX_LOST_KEEP_ALIVE("mvnd.maxLostKeepAlive", null, 30, false),
/** /**
* The minimum number of threads to use when constructing the default {@code -T} parameter for the daemon. * The minimum number of threads to use when constructing the default {@code -T} parameter for the daemon.
* This value is ignored if the user passes @{@code -T}, @{@code --threads} or {@code -Dmvnd.threads} on the command * This value is ignored if the user passes @{@code -T}, @{@code --threads} or {@code -Dmvnd.threads} on the command