Describe the bug
When setting the timeUnit configuration, it always overrides any other setup OutputTimeUnit. For example you set the gradle configuration timeUnit to ms, you can no longer use the @OutputTimeUnit annotation to change it for a specific class or method. When removing the configurations, the annotations start working again.
To Reproduce
Steps to reproduce the behavior:
Add timeUnit = "ms" to your jmh configuration in the build.gradle.kts file
Add a @OutputTimeUnit(TimeUnit.NANOSECONDS) to a method or class benchmark.
The result output is alway set to the value defined in the gradle configuration. When removing the configuration, setting it on the class and method level works with different values
Describe the bug When setting the
timeUnit
configuration, it always overrides any other setupOutputTimeUnit
. For example you set the gradle configuration timeUnit toms
, you can no longer use the@OutputTimeUnit
annotation to change it for a specific class or method. When removing the configurations, the annotations start working again.To Reproduce Steps to reproduce the behavior:
timeUnit = "ms"
to your jmh configuration in thebuild.gradle.kts
file@OutputTimeUnit(TimeUnit.NANOSECONDS)
to a method or class benchmark.