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
[autorevert] Fix bug on job retrival for autorevert lambda (#6979)
After fixing the bug, the new statistics are:
```
==================================================
SUMMARY STATISTICS
==================================================
Workflow(s): Lint, trunk, pull, inductor, linux-binary-manywheel
Timeframe: 4320 hours
Commits checked: 33519
Auto revert patterns detected: 1345
Actual reverts inside auto revert patterns detected (precision): 219 (16.3%)
Total revert commits in period: 585
Revert categories:
nosignal: 202 (34.5%)
ghfirst: 156 (26.7%)
uncategorized: 104 (17.8%)
ignoredsignal: 68 (11.6%)
weird: 45 (7.7%)
landrace: 10 (1.7%)
Total reverts excluding ghfirst: 429
Reverts (excluding ghfirst) that dont match any auto revert pattern detected (recall): 250 (58.3%)
Per workflow precision:
Lint: 45 reverts out of 75 patterns (60.0%) [excluding ghfirst: 41 (54.7%)]
trunk: 30 reverts out of 136 patterns (22.1%) [excluding ghfirst: 28 (20.6%)]
pull: 104 reverts out of 859 patterns (12.1%) [excluding ghfirst: 92 (10.7%)]
inductor: 39 reverts out of 269 patterns (14.5%) [excluding ghfirst: 38 (14.1%)]
linux-binary-manywheel: 1 reverts out of 6 patterns (16.7%) [excluding ghfirst: 0 (0.0%)]
```
The main bug is that when checking for commits before/after with the
same job, it actually concatenated all commits+jobs before and after,
instead of only returning the next one.
I added also the ergonomics for lambda invocation
---------
Co-authored-by: Ivan Zaitsev <[email protected]>
0 commit comments