5f96daa8a5
It seems like this got confused when initially added [1,2]. The confusion affects the lag check [3], which only send an email in the past, but will raise a builder failure after [4] landed if there is a gap for more than 4 commits. [1] https://crsrc.org/i/infra/services/lkgr_finder/config/default_cfg.pyl?q=allowed_gap [2] https://crsrc.org/i/infra/services/lkgr_finder/test/lkgr_lib_test.py?q=allowed_gap [3] https://crsrc.org/i/infra/services/lkgr_finder/lkgr_lib.py;l=500?q=allowed_lag [4] https://crrev.com/c/3599253 Bug: chromium:1317669 Change-Id: I23726957439b03dced0fc0038ee65a3108f88fea Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/259874 Auto-Submit: Alex Schulze <alexschulze@google.com> Reviewed-by: Christoffer Jansson <jansson@webrtc.org> Commit-Queue: Christoffer Jansson <jansson@webrtc.org> Cr-Commit-Position: refs/heads/main@{#36642}