cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berenguer Blasi (Jira)" <>
Subject [jira] [Issue Comment Deleted] (CASSANDRA-16176) Python dtests should run at debug
Date Mon, 09 Nov 2020 09:30:00 GMT


Berenguer Blasi updated CASSANDRA-16176:
    Comment: was deleted

(was: Meh.. must be some expiring session or God knows what. Go to the [test run|]
-> artifacts -> select a random log file and check it has the DEBUG statements you're

> Python dtests should run at debug
> ---------------------------------
>                 Key: CASSANDRA-16176
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message