Skip to content

[CASSANDRA-21757][trunk] Report failed JMH benchmarks in CI as failed JUnit tests - #5263

Closed
netudima wants to merge 1 commit into
apache:trunkfrom
netudima:CASSANDRA-21757-trunk
Closed

netudima wants to merge 1 commit into
apache:trunkfrom
netudima:CASSANDRA-21757-trunk

Conversation

@netudima

Copy link
Copy Markdown
Contributor

A failed benchmark failed its whole microbench CI cell, and so the pipeline. .build/sh/jmh-junit-report.py now renders the JMH run as JUnit xml, a TEST-*.xml per benchmark class, so Jenkins lists a failed benchmark as a failed test and marks the build unstable. CI runs JMH with -foe false, so a failure no longer stops the rest of its split. A run that does not complete still fails.

patch by Dmitry Konstantinov; reviewed by TBD for CASSANDRA-21757
Assisted-by: LLM

A failed benchmark failed its whole microbench CI cell, and so the pipeline.
.build/sh/jmh-junit-report.py now renders the JMH run as JUnit xml, a TEST-*.xml
per benchmark class, so Jenkins lists a failed benchmark as a failed test and
marks the build unstable.  CI runs JMH with -foe false, so a failure no longer
stops the rest of its split.  A run that does not complete still fails.

patch by Dmitry Konstantinov; reviewed by TBD for CASSANDRA-21757
Assisted-by: LLM
@netudima

Copy link
Copy Markdown
Contributor Author

Merged as dd48703

@netudima netudima closed this Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants