> On Dec 14, 2018, at 1:05 PM, Chris Hostetter <[email protected]> wrote: > ...all of the recent failures have come from sarowe's jenkins box ... but i'm > not sure if that indicates a problem with running these tests on his machine, > or if he's just running nightly tests more often then other jenkins hosts?
Thanks for the heads-up Hoss. I looked at the logs and these all are suite timeouts; other Lucene tests also affected, e.g. Test2BPostings and TestGeo3DPoint. My Jenkins runs module testing in parallel, so I'd guess in these cases that there are (way) more active threads than CPU cores, which would slow tests down. I also use the box my Jenkins runs on for other tasks, which could be another cause of resourse starvation here. I'll take a look at how the Nightly jobs run on my Jenkins and see if I can improve the situation. Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
