|
From: Juri L. <no...@gi...> - 2026-08-17 18:00:07
|
Branch: refs/heads/develop Home: https://github.com/eXist-db/exist Commit: 847d8878174040c8b30dbdea55629898c58de51c https://github.com/eXist-db/exist/commit/847d8878174040c8b30dbdea55629898c58de51c Author: duncdrum <d.p...@me...> Date: 2026-08-17 (Mon, 17 Aug 2026) Changed paths: M .github/workflows/ci-benchmarks.yml Log Message: ----------- [bugfix] Activate perf-tests profile in ci-benchmarks.yml 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 (#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 <no...@an...> Commit: 225680c2fb7779c3cee208fe6cacfb42c236fa0e https://github.com/eXist-db/exist/commit/225680c2fb7779c3cee208fe6cacfb42c236fa0e Author: Juri Leino <gi...@li...> Date: 2026-08-17 (Mon, 17 Aug 2026) Changed paths: M .github/workflows/ci-benchmarks.yml Log Message: ----------- Merge pull request #6641 from duncdrum/fix/jmh-benchmarks-perf-tests-profile Fix ci-benchmarks.yml: activate perf-tests profile Compare: https://github.com/eXist-db/exist/compare/c825bb024ecf...225680c2fb77 To unsubscribe from these emails, change your notification settings at https://github.com/eXist-db/exist/settings/notifications |