Perhaps this is the duplication of all (or at least most) previously existing tests for running under Python 3. I agree that this is excessive; we should probably split out Py2, Py3, and the linters into separate targets.
We could look into using detox or retox to parallelize the testing as well. (The issue last time was suppression of output on timeout, but that can be worked around by adding timeouts to the individual tox targets.) On Fri, Mar 8, 2019 at 11:26 PM Mikhail Gryzykhin <mig...@google.com> wrote: > Hi everyone, > > Seems that our python pre-commits grow up in time really fast > <http://104.154.241.245/d/_TNndF2iz/pre-commit-test-latency?orgId=1&from=now-6M&to=now> > . > > Did anyone follow trend or know what are the biggest changes that happened > with python lately? > > I don't see a single jump, but duration of pre-commits almost doubled > since new year. > > [image: image.png] > > Regards, > --Mikhail > > Have feedback <http://go/migryz-feedback>? >
