[jira] [Commented] (CASSANDRA-16176) Python dtests should run at debug

["Brandon Williams (Jira)" <ji...@apache.org>]

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

Brandon Williams commented on CASSANDRA-16176:
----------------------------------------------

I wholesale replaced 'INFO' with 'DEBUG': https://app.circleci.com/pipelines/github/driftx/cassandra?branch=CASSANDRA-16176

Nothing broke, but it also didn't produce debug output (outside of CCM, which is odd.)

> Python dtests should run at debug
> ---------------------------------
>
>                 Key: CASSANDRA-16176
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16176
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Brandon Williams
>            Priority: Normal
>
> At least in our circle configs, we are specifying --log-level="INFO" which often leaves us with nothing to go on when we have a flaky test that only fails in a certain environment.  In general it would be more useful to always run at DEBUG. 



--
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