You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using pytest-benchmark 4.0.0 with "pytest-benchmark compare 0001 0002", it could happen that test time of one case in 0001.json is 1.5s, while the corresponding one in 0002.json is 0.5s, which results to 1.5s and 500ms in the output text file and makes it not so clear for interpretation. The --benchmark-time-unit option introduced in 5.0.0 might be utilized to set the time scale in the output text file. Could it be cherry-picked also to 4.0.0 as well, maybe with extra work? Thank you for the time.
5.0.0 (2024-10-29)
Added the --benchmark-time-unit cli option for overriding the measurement unit used for display. Contributed by Tony Kuo in #257.
With regards,
Jing
The text was updated successfully, but these errors were encountered:
Dear all,
When using pytest-benchmark 4.0.0 with "pytest-benchmark compare 0001 0002", it could happen that test time of one case in 0001.json is 1.5s, while the corresponding one in 0002.json is 0.5s, which results to 1.5s and 500ms in the output text file and makes it not so clear for interpretation. The --benchmark-time-unit option introduced in 5.0.0 might be utilized to set the time scale in the output text file. Could it be cherry-picked also to 4.0.0 as well, maybe with extra work? Thank you for the time.
5.0.0 (2024-10-29)
Added the --benchmark-time-unit cli option for overriding the measurement unit used for display. Contributed by Tony Kuo in #257.
With regards,
Jing
The text was updated successfully, but these errors were encountered: