-
Notifications
You must be signed in to change notification settings - Fork 112
Fix time_diff* and time_remove benchmarks to account for long RFed interfaces #7502
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
Conversation
…d revision arg etc Only with fresh asv 0.6.0 which started to exit with exit code 2 if any benchmark failed, we finally had to pay attention to those long failing benchmarks. We have removed the option 'revision' so long ago but first didn't mention and then just ignored. For that and time_remove I also made it into dataset method invocation since otherwise it was not finding the dataset any longer given the path to it (didn't investigate deeper).
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## maint #7502 +/- ##
==========================================
+ Coverage 91.55% 91.56% +0.01%
==========================================
Files 325 325
Lines 43443 43443
Branches 5827 5827
==========================================
+ Hits 39774 39780 +6
+ Misses 3654 3648 -6
Partials 15 15 ☔ View full report in Codecov by Sentry. |
99c5084
to
a1fc3e3
Compare
It still exists with code 2. The output is so long that it is not very accessible why this is the case. |
I think it's is hailing since it is the second run which uses main branch version of benchmark which isn't fixed - just search for "failed" to find
Overall, I would merge and go from there |
ok, I am taking responsibility to fix it up further if there is more to do after the merge... let's proceed to make CI green again! |
ok, I am taking responsibility to fix it up further if there is more to do after the merge... let's proceed to make CI green again! |
PR released in |
Only with fresh asv 0.6.0 which started to exit with exit code 2 if any benchmark failed, we finally had to pay attention to those long failing benchmarks. We have removed the option 'revision' so long ago but first didn't mention and then just ignored. For that and time_remove I also made it into dataset method invocation since otherwise it was not finding the dataset any longer given the path to it (didn't investigate deeper).