-
-
Notifications
You must be signed in to change notification settings - Fork 963
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom SimpleJob
Id ignored when the MinIterationTime
attribute is used.
#2473
Comments
Leaving some findings here to (hopefully) help the next person. I noticed that I can recreate the issue with other attributes like [IterationTime(100)] or [MinInvokeCount(2)] as long as it has .IsMutator set to true. The ResolvedId is set in the Job class So I assume somewhere along the way IdCharacteristic loses it's value. One method of interest with my comments added. Found in the ImmutableConfigBuilder class:
I also kept testing old commits and the issue was there as well. I went as far as 7/26/23 d93490d and this was still an issue. |
@m-kovac @timcassell Ok I figured it out. PR submitted. |
Hello, just identified the issue that causes all Jobs declared as attributes to have their Id's replaced with random Job names in the summary table if the
MinIterationTime
attribute is used.Steps to reproduce:
Create benchmark class and add two
SimpleJob
attributes as well asAllStatisticsColumn
to show the Job Id. Here I just use the default example from README.In this case the table shows correct Job Id in the table( included only 2 lines for brevity)
In case when also the
MinIterationTIme
attribute is added, the table shows the randomly generated Job IdThe text was updated successfully, but these errors were encountered: