Closed sxa closed 4 years ago
Are the tests doing anything that would interfere with the jenkins process on the machine (which is a java process running as the same user as the tests)?
Not sure about that. However tests haven't been changed recently and work good for a while. Any machine configuration changed? Like jenkins or plugin updates?
Update: I see this problem on test-softlayer-ubuntu1604-x64-1 (https://ci.adoptopenjdk.net/view/work%20in%20progress/job/Grinder/65/console)
But I do not see it on test-packet-ubuntu1604-x64-2 (https://ci.adoptopenjdk.net/view/work%20in%20progress/job/Grinder/66/console) even if I run it a second time on the same machine (https://ci.adoptopenjdk.net/view/work%20in%20progress/job/Grinder/67/console)
Is there a difference between the two machines that might provide clues?
I've bounced the jenkins agent on test-softlayer-ubuntu1604-x64-1
so we'll see if it recurs
Not seen any issues in this area recently, therefore closing to get this off the issues list
I've had reports of three of our test machines having issues today with an error similar to the following showing in the logs:
This has so far been reported on
test-softlayer-ubuntu1604-x64-1
andtest-marist-ubuntu1604-s390x-1
today. Both appear to have cleared with a disconnect / relaunch of the slave. Reason unclear at present (and is clearly not limited to any specific cloud provider) but keeping this issue around to track any more instances.This had also happened previously
test-osuosl-ppc64le-ubuntu-16-04-1
from June 7 to June 26.