Michael Semb Wever created CASSANDRA-20157:
----------------------------------------------
Summary: Timing info in Jenkinsfile
Key: CASSANDRA-20157
URL: https://issues.apache.org/jira/browse/CASSANDRA-20157
Project: Apache Cassandra
Issue Type: Improvement
Components: CI
Reporter: Michael Semb Wever
Assignee: Michael Semb Wever
Tuning the number of splits, and generally analysing where timeouts are (and
will be) happening, is currently more difficult than it needs to be.
Splits are created dynamically in the Jenkinsfile, with a fixed number of
splits per test type. In trunk there's >900 splits. While the blue ocean ui
can help highlight which splits have timed out (past the one hour per-split
timeout) twice (each split will retry once), it remains difficult to scroll
through the blue ocean screen, to identify splits that only timed out once, and
to see which splits are heavier (taking longer) than their counterparts and the
timing trends of splits over time.
A simple log line reporting time taken for each split attempt solves all this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
