[
https://issues.apache.org/jira/browse/CASSANDRA-16176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17207320#comment-17207320
]
Michael Semb Wever commented on CASSANDRA-16176:
------------------------------------------------
For ci-cassandra.a.o this was fixed with
https://github.com/apache/cassandra-builds/commit/95aad36a88baccda5a89a26a0cbeea8333902062
The option {{--log-level=INFO}} was replaced with {{--log-cli-level=DEBUG}}.
The debug logging is available in the jenkins builds console, as well as
uploaded and saved on nightlies.a.o in the {{test_stdout.txt.xz}} file.
For example:
https://nightlies.apache.org/cassandra/Cassandra-devbranch-dtest/label=cassandra,split=1/51/
ref: https://the-asf.slack.com/archives/CK23JSY2K/p1601712135094500
> 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: Brandon Williams
> Priority: Normal
> Fix For: 4.0-beta
>
>
> 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]
