You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Abraham Fine (JIRA)" <ji...@apache.org> on 2017/06/06 19:59:18 UTC

[jira] [Comment Edited] (ZOOKEEPER-2799) Separate logs generated by tests in jenkins jobs when tests are run in parallel

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

Abraham Fine edited comment on ZOOKEEPER-2799 at 6/6/17 7:59 PM:
-----------------------------------------------------------------

So it appears this already happens in the xml files that are output to `build/test/logs`. Sometimes, in the Jenkins test results these become truncated. Perhaps this can be remedied by setting `build/test/logs` as an artifact to publish?

[~hanm] would you be willing to make this change?


was (Author: abrahamfine):
So it appears this already happens in the xml files that are output to `build/test/logs`. Sometimes, in the Jenkins test results these become truncated. Perhaps this can be remedied by setting `build/test/logs` as an artifact to publish?

@hanm would you be willing to make this change?

> Separate logs generated by tests in jenkins jobs when tests are run in parallel
> -------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2799
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2799
>             Project: ZooKeeper
>          Issue Type: Bug
>            Reporter: Abraham Fine
>            Assignee: Abraham Fine
>
> We often run our tests in parallel (for example, our GitHub hook), this means the tests are often difficult to debug since all of the tests are logging to the console and become interwoven. We should have each test log to its own file.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)