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

Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2020/12/10 19:19:00 UTC

[jira] [Commented] (CASSANDRA-16324) NodeToolResult should always capture stdout/err

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

David Capwell commented on CASSANDRA-16324:
-------------------------------------------

in 16200, the comment was made that this was an assumption based on there being two constructors, but 2.2, 3.0, 3.11, and trunk all use the constructor which takes stdout/stderr; we have this here for backwards compatibility only.

> NodeToolResult should always capture stdout/err
> -----------------------------------------------
>
>                 Key: CASSANDRA-16324
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16324
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Test/dtest/java
>            Reporter: Berenguer Blasi
>            Assignee: Berenguer Blasi
>            Priority: Normal
>             Fix For: 4.0
>
>
> During CASSANDRA-16200 it was noticed stdout/err was only being captured selectively whereas it should be _always_ captured. See 16200 for details.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org