Fix ci-benchmarks.yml: activate perf-tests profile - #6641
Merged
line-o merged 1 commit intoAug 17, 2026
Conversation
exist-core-jmh and exist-indexes-jmh are gated behind the perf-tests Maven profile in the root pom.xml, not part of the default reactor. Every run of the JMH Benchmarks workflow (eXist-db#6608) has failed since it merged, all three runs erroring identically at the first build step: [ERROR] Could not find the selected project in the reactor: exist-core-jmh Add -Pperf-tests to all three mvn invocations that select these modules via -pl (both `install -am` build steps, and the `exec:exec` step for exist-indexes-jmh). The `java -jar` step for exist-core-jmh needs no change - it invokes the already-built jar directly, no reactor lookup. Verified locally: `mvn install -Pperf-tests -pl exist-core-jmh -am` and `-pl exist-indexes-jmh -am` both build clean; `mvn exec:exec -Pperf-tests -pl exist-indexes-jmh -Dbenchmark.args="RangeEqWhereClauseBenchmark ..."` runs end to end. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
dizzzz
approved these changes
Aug 17, 2026
reinhapa
approved these changes
Aug 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Every run of the JMH Benchmarks workflow (added in #6608) has failed since merge — all three runs (2 scheduled, 1 manual dispatch) fail identically at the first build step:
exist-core-jmh/exist-indexes-jmhare gated behind theperf-testsMaven profile in the rootpom.xml, not part of the default reactor —mvn -pl <module>can't find them without-Pperf-testsactive.Fix
Add
-Pperf-teststo all threemvn -plinvocations that select these modules: bothinstall -ambuild steps, and theexec:execstep forexist-indexes-jmh. Thejava -jarstep forexist-core-jmhneeds no change — it runs the already-built jar directly, no reactor lookup involved.Test plan
mvn install -Pperf-tests -pl exist-core-jmh -am -DskipTests— builds cleanmvn install -Pperf-tests -pl exist-indexes-jmh -am -DskipTests— builds cleanmvn exec:exec -Pperf-tests -pl exist-indexes-jmh -Dbenchmark.args="RangeEqWhereClauseBenchmark -wi 1 -i 1 -f 1 -w 3s -r 3s -p termCount=5"— runs end to endworkflow_dispatchrun pending after merge🤖 Generated with Claude Code