Skip to content

Commit

Permalink
Disable output caching for jmh module (#5651)
Browse files Browse the repository at this point in the history
**Motivation**

We often run benchmarks several times without modifying the code.
However, with gradle up-to-date checks, we can often see that only the
first run actually applies benchmarks.
I think it's reasonable that the jmh task output caching is always
disabled

**Modifications**

Always disable output caching for jmh tasks

**Result**

It is easier to run benchmarks
  • Loading branch information
jrhee17 authored May 2, 2024
1 parent d526c38 commit 0d5b520
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions benchmarks/jmh/build.gradle
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,11 @@ jmh {
}
}

// Disable output caching so that benchmarks are not skipped on the second run.
tasks.jmh.outputs.upToDateWhen {
false
}

// Workaround a bug where the conflict of output path between 'benchmarks.jmh' and 'benchmarks.test' in IDEA
project.afterEvaluate {
idea {
Expand Down

0 comments on commit 0d5b520

Please sign in to comment.