05/31/2019, 10:34 AM
Timed out, and I’m not sure how to diagnose why:
05/31/2019, 2:59 PM
that's v1 timing out, i think?
...oh. or it's just that the whole thing took more than 50 minutes.
05/31/2019, 3:03 PM
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…
05/31/2019, 3:57 PM
So that is due to
timing out. We should set a higher value for it, like
Alternatively, we could make the V2 test runner faster. See
05/31/2019, 4:04 PM
whoops, sorry. the ticket i meant to reference was:
but also, worth noting that pushing forward on remoting is also a way to get caching.