IIRC currently, post-commit doesn't run pre-commits. However we have precommit_cron jobs that run pre-commits periodically. However it sums up to dozens of jobs that is really hard to monitor.
If we split things even further, we definitely need to combine result into something more easily trackable. Also making post-commits bigger is not that good idea either, since it will make them even more flaky and any PR that needs to run them can get stuck forever. Main point is that we want to do some work around improving monitoring, not simply make more post-commits, or bigger post-commits. On Tue, Oct 29, 2019 at 9:56 AM Chad Dombrova <[email protected]> wrote: > > +1 for splitting pre-commit tests into smaller modules. However in this >> case we need to run all the small tests periodically and have some combined >> flag or dashboard for regular monitoring. Otherwise we might not run/check >> on big amount of tests. >> > > post-commit seems like the best place for that, no? > > >
