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

Berenguer Blasi commented on CASSANDRA-16176:
---------------------------------------------

TRACE is indeed heavier so I am happy to leave it at DEBUG and we can change it 
later if needed. I have pushed and ran CI for low, mid and high res. The 3 
display DEBUG for the nodes logs, ccm and the py test itself. Look for 
{{test_split}} in the CI run {{Artifacts}} tab. Then look inside the 
{{stdout.txt}} for that executor for {{Run stress to ensure data is readable}} 
to locate a py test DEBUG message:
- HIGH: 
[j11|https://app.circleci.com/pipelines/github/bereng/cassandra/179/workflows/61825d09-50b5-475f-b8af-779381a741c8]
 
[j8|https://app.circleci.com/pipelines/github/bereng/cassandra/179/workflows/9bf31e85-9b86-43da-82a7-130af992cc1d]
- MID: 
[j11|https://app.circleci.com/pipelines/github/bereng/cassandra/178/workflows/5791ee2e-a23a-4474-b2e2-0a12f3eafe36]
 
[j8|https://app.circleci.com/pipelines/github/bereng/cassandra/178/workflows/7a5e5dce-ce05-49c8-8bb1-5ff23b839666]
- LOW: 
[j11|https://app.circleci.com/pipelines/github/bereng/cassandra/177/workflows/663735e6-0acf-455c-8b85-545bbd1d9ea7]
 
[j8|https://app.circleci.com/pipelines/github/bereng/cassandra/177/workflows/34090602-f24c-4b10-9066-51a3f6090f0f]

If this is what you needed it is ready to merge imo.

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

Reply via email to