[
https://issues.apache.org/jira/browse/CASSANDRA-16176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228447#comment-17228447
]
Berenguer Blasi edited comment on CASSANDRA-16176 at 11/9/20, 9:27 AM:
-----------------------------------------------------------------------
Meh.. must be some expiring session or God knows what. Go to the [test
run|https://app.circleci.com/pipelines/github/bereng/cassandra/177/workflows/34090602-f24c-4b10-9066-51a3f6090f0f/jobs/1381]
-> artifacts -> select a random log file and check it has the DEBUG statements
you're expecting.
was (Author: bereng):
Meh.. must be some expiring session or God knows what. Go to the [test
run|https://app.circleci.com/pipelines/github/bereng/cassandra/177/workflows/34090602-f24c-4b10-9066-51a3f6090f0f]
-> artifacts -> select a random log file and check it has the DEBUG statements
you're expecting.
> 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
>
> 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]
