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

Patrick Bannister commented on CASSANDRA-14371:
-----------------------------------------------

Markus Eriksson, I'm still studying the Jenkins build to confirm this, but my 
working theory is that this Jenkins build is using ccm on the master branch 
instead of on the cassandra-test branch. Right now, on the master branch, 
handle_external_tool_process in ccmlib/node.py doesn't decode stdout or stderr 
before returning it - that behavior is only on the cassandra-test branch.

What is our preferred ccm build for testing? I've been using its cassandra-test 
branch for my tests, since that's what the cassandra-dtest requirements.txt 
specifies right now.

> dtest failure: sstablesplit_test.TestSSTableSplit.test_single_file_split
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14371
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14371
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Marcus Eriksson
>            Priority: Major
>
> https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-trunk-dtest/489/testReport/sstablesplit_test/TestSSTableSplit/test_single_file_split/
> {code}
>         for (stdout, stderr, rc) in result:
>             logger.debug(stderr)
> >           failure = stderr.find("java.lang.AssertionError: Data component 
> > is missing")
> E           TypeError: a bytes-like object is required, not 'str'
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to