You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/10/02 10:13:21 UTC

[jira] [Commented] (SUREFIRE-1289) forkedProcessTimeoutInSeconds should not use ping timer of 10 seconds but 0.1 sec period timer

    [ https://issues.apache.org/jira/browse/SUREFIRE-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15540134#comment-15540134 ] 

Hudson commented on SUREFIRE-1289:
----------------------------------

SUCCESS: Integrated in Jenkins build maven-surefire #1629 (See [https://builds.apache.org/job/maven-surefire/1629/])
[SUREFIRE-1289] forkedProcessTimeoutInSeconds should not use ping timer (tibor17: rev b2488b64567934c341d2643856d57dd48aa88359)
* (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkStarter.java


> forkedProcessTimeoutInSeconds should not use ping timer of 10 seconds but 0.1 sec period timer
> ----------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1289
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1289
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>             Fix For: 2.19.2
>
>
> Fix typo in class {{ForkStarter.java}} where method {{triggerTimeoutCheck()}} used
> {{pingThreadScheduler}} instead of {{timeoutCheckScheduler}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)