[ https://issues.apache.org/jira/browse/CASSANDRA-19050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805499#comment-17805499 ]
Benjamin Lerer edited comment on CASSANDRA-19050 at 1/11/24 10:45 AM: ---------------------------------------------------------------------- I updated the patch to deal with that [here|https://github.com/blerer/cassandra/commit/f41c39f4ca7c29d602b56ce2296632a853c7fe7c]. Another option would have been to switch to a 3 digits approach. [CI|https://app.circleci.com/pipelines/github/blerer/cassandra/369/workflows/1bc6228e-27de-4a5d-aca5-317e2fdd3a39] was (Author: blerer): I updated the patch to deal with that [here|https://github.com/blerer/cassandra/commit/f41c39f4ca7c29d602b56ce2296632a853c7fe7c]. Another option would have been to switch to a 3 digits approach. > Enhanced usage of test method names in CQLTester for better test debugging > -------------------------------------------------------------------------- > > Key: CASSANDRA-19050 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19050 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit > Reporter: Berenguer Blasi > Assignee: Berenguer Blasi > Priority: Normal > Fix For: 5.0-rc, 5.x > > > All views, tables, ks,... created in CQLTester are of the form {{table_00}}: > - While debugging tests and flakies this makes it really hard to match logs > to test methods. > - Some async operations can spill log lines from a previous test method into > the next's log lines which is incredibly confusing > - It's hard on the eyes and easy to mix up > - When comparing logs from 2 different branches, envs,... it's really hard to > match logs > The proposed solution is for {{CQLTester}} to decorate these with the test > name. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org