[
https://issues.apache.org/jira/browse/CASSANDRA-16176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16176:
-----------------------------------------
Fix Version/s: 4.0-beta4
Source Control Link:
https://github.com/apache/cassandra/commit/63e8e7d855ef588380eba09b10ae21ea7b97166b
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed, thanks!
> Python dtests should run at debug
> ---------------------------------
>
> Key: CASSANDRA-16176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16176
> Project: Cassandra
> Issue Type: Improvement
> Components: CI
> Reporter: Brandon Williams
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 4.0-beta, 4.0-beta4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
