Hi all!

I’ve noticed that we’re back in the state where it’s tough to get a clean PR 
Jenkins test run. Spot checking the top ~10 pull request runs show this doesn’t 
appear to be an issue with just my PRs :P

I know we have some chronic flaky tests, but I’ve seen at least two other 
classes of problems:

1. Jenkins test runners hanging and eventually timing out
2. Intra Jenkins-container/pod/VM/machine/turtle communication issues

How do we go about diagnosing test runs that fail in such an opaque fashion?

Thanks!
Kirk

Reply via email to