Please sign in to comment.
Run lint shard with Python 2 during daily CI instead of nightly cron …
…job (#7391) ### Problem The lint shard is a very cost-effective way to prevent Py2 regressions. For only about 8 minutes of extra total worker time, we can ensure we are always using defined symbols, for example. This would have prevented #7381 for example. In fact, that PR didn't even properly fix the issue. Running the lint shard during daily CI would have both prevented the issue in the first place and ensured the hotfix worked. ### Solution Run the lint shard with both Py2 and Py3 during daily CI. No longer run during nightly cron job. Also fix the issue #7381 was supposed to fix. ### Result We should have less Python 2 regressions. While CI will take 10 minutes longer of total worker time, the wall time should not be changed (beyond when we don't have enough workers). This extra time is worth the lowered risk of regressions.
- Loading branch information...
Showing with 6 additions and 2 deletions.