Is there a reason why each integration test has a really aggressive 60 second timeout?

do you mean by default? i think that's the default for

python_tests()

and we don't try to automatically change it when the target has

tags={'integration'}

, although that wouldn't be a bad idea, it's just hard to know what the right default should be. you can add

timeout = 240

or whatever makes sense

i did change the default just so I can get past all the tests timing out, but it seems kind of aggressive for an integration test

yes

i suspect this will be less of a problem as time goes on, so its not a big deal, just a little frustrating when my tests were timing out

that makes sense

The main problem is that we only actually run tests on CI both sharded (which means we don't run full targets) and together in clumps (which sums the timeouts of each target). So all our timeout numbers are meaningless.

sounds like an excuse to scorch some earth