Timed out, and I’m not sure how to diagnose why: <...
# development
a
Timed out, and I’m not sure how to diagnose why: https://travis-ci.org/pantsbuild/pants/jobs/539430253
w
that's v1 timing out, i think?
...oh. or it's just that the whole thing took more than 50 minutes.
a
Yeah, it looks like the whole thing took >50 minutes, so got `SIGKILL`’d, and I can’t see from the output what test it was in…
h
So that is due to
travis_wait
timing out. We should set a higher value for it, like
travis_wait 65
https://github.com/pantsbuild/pants/blob/master/.travis.yml#L958 Alternatively, we could make the V2 test runner faster. See https://github.com/pantsbuild/pants/issues/7795
w
whoops, sorry. the ticket i meant to reference was: https://github.com/pantsbuild/pants/issues/6898
but also, worth noting that pushing forward on remoting is also a way to get caching.