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

Posted to proton@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/02/15 14:48:18 UTC

[jira] [Commented] (PROTON-1132) Timeout in valgrind test

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

ASF subversion and git services commented on PROTON-1132:
---------------------------------------------------------

Commit 8293164d8755f91df08b4c70f586d1862aa84016 in qpid-proton's branch refs/heads/master from Clifford Jansen
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=8293164 ]

PROTON-1132: Timeout in valgrind test


> Timeout in valgrind test
> ------------------------
>
>                 Key: PROTON-1132
>                 URL: https://issues.apache.org/jira/browse/PROTON-1132
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: cpp-binding
>    Affects Versions: 0.13.0
>            Reporter: Cliff Jansen
>            Assignee: Cliff Jansen
>
> Since PROTON-1115 was fixed some CI tests are failing with timeouts.  Working theory is that re-introducing valgrind just takes longer on some slower test machinery.  Will increase the timeout (doesn't slow down a successful run) and close the JIRA if runs complete successfully.



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