[
https://issues.apache.org/jira/browse/CALCITE-6470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stamatis Zampetakis resolved CALCITE-6470.
------------------------------------------
Resolution: Fixed
Fixed in
[7d9b639cd41ff7b3e3c81a705da5a38308c0b8ac|https://github.com/apache/calcite/commit/7d9b639cd41ff7b3e3c81a705da5a38308c0b8ac].
Thanks [~caicancai] for the review!
> Run specific JMH benchmarks without modifying sources
> -----------------------------------------------------
>
> Key: CALCITE-6470
> URL: https://issues.apache.org/jira/browse/CALCITE-6470
> Project: Calcite
> Issue Type: Improvement
> Components: build
> Reporter: Stamatis Zampetakis
> Assignee: Stamatis Zampetakis
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.38.0
>
>
> Currently we can run *all* JMH benchmarks of the project using the "jmh"
> Gradle task.
> {code:java}
> ./gradlew :ubenchmark:jmh
> {code}
> In many cases, we don't want to run all benchmarks but only one (or few) and
> this is not possible without modifying the Gradle build files (see
> https://github.com/melix/jmh-gradle-plugin/issues/152).
> The goal of this ticket is to add a (project) property (i.e., jmh.includes)
> to select the desired benchmarks via a regular expression that can be passed
> in the command line.
> {code:java}
> ./gradlew :ubenchmark:jmh -Pjmh.includes=ParserBenchmark
> {code}
> For example, the command above would run only the ParserBenchmark.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)