cassandra-commits mailing list archives

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

     [ https://issues.apache.org/jira/browse/CASSANDRA-16176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Berenguer Blasi updated CASSANDRA-16176:
----------------------------------------
    Comment: was deleted

(was: 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.)

> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message