Open loonatick-src opened 8 months ago
Thanks for the report, unfortunately away for a couple of weeks and won't have time to check on this until then, sorry for delay.
Had a Quick Look at this now, this is not expected - will have a look at it, in the meantime generating a new baseline with the new factor should make things work.
Note to self:
result.timeUnits = base.timeUnits
is invalid, we should instead scale the percentile results to base when they differ.
to
This shows up like so when using
swift package benchmark baseline compare
It appears that the new benchmark is not scaled and this caused some confusion. Is this the intended behavior?