fix: Fix occasionally incorrect unit in some tables [2/4]#329
fix: Fix occasionally incorrect unit in some tables [2/4]#329hassila merged 1 commit intoordo-one:mainfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #329 +/- ##
==========================================
+ Coverage 69.41% 69.41% +0.01%
==========================================
Files 33 33
Lines 4053 4051 -2
==========================================
- Hits 2813 2812 -1
+ Misses 1240 1239 -1
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
|
Would you mind rebasing this on the latest main? I merged PR 1/4 with slight changes. |
aac61b6 to
1b742a8
Compare
1b742a8 to
d88a154
Compare
|
@hassila done |
|
Do you have an example that generated the output from the screenshots? Would be good to understand the configuration used for the test. |
|
@hassila not 100% sure, but try this: Benchmark.defaultConfiguration.units = [<metric>: .kilo]and make sure the output should not be in kilos (but observe that it will be, without this PR). |
|
I just noticed you asked for an example not just the configuration, I'm already off the desk though so I'll grab that tomorow. |
|
This is what i think was the benchmark when the issue here happened (although i think even the new benchmarks would have this issue): I think you can just compare 2 strings instead of 2 |
|
Thanks, I've reproduced this and verified the fix with: swift package --allow-writing-to-package-directory benchmark thresholds update --target Basic --filter "Equality_Check_Identical_Throughput"
swift package benchmark thresholds check --target Basic --filter "Equality_Check_Identical_Throughput"(just a note for the future) |
|
Thanks! |
Description
Actually resolves #277. EDIT: or actually not sure if this solves the same issue. But solves an issue anyway.
Examples:
Incorrect label, saying "M" aka "Mega" (or I guess "Millions" also reads fine):
Correct label, saying "K" aka "Kilo":
To be completely clear, both these images are 100% correct other than the first image mentioning "M" aka 10^6.
Feel free to review on your own schedule.
How Has This Been Tested?
Manually in my PRs.
Minimal checklist:
DocCcode-level documentation for any public interfaces exported by the package