re: ``` Cannot contact i-09a7ea9f1f400ab9b: java.lang.InterruptedException Could not connect to i-09a7ea9f1f400ab9b to send interrupt signal to process ``` we have an 8 hour time limit set on the zfstest runs, so if any run takes longer than that, it'll be killed by the Jenkins framework, and the result is a message like this.. additionally, I can see that the zfstest script was running for nearly 8 hours; the UI shows `7h 59m 15s`:
 So that's all a good indicator that we hit the time limit. Looking at some of the recent "master" branch runs, [here](http://jenkins.open-zfs.org/blue/organizations/jenkins/openzfs%2Fopenzfs/activity/?branch=master), zfstest appears to usually take between 4 and 6 hours to complete. So, the question is, why was it still running after 8 hours of runtime? I have seen this timeout trigger before, on code that passed like normal when run a second time, so this might not have anything to do with this specific change, but it would be good to verify that (e.g. double check that this change isn't making some of the tests run longer than normal, and/or run the tests again to see if it hits the same timeout). The `zdb` error is almost certainly due to this change, so that'll need to be addressed. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/openzfs/openzfs/pull/124#issuecomment-309332490 ------------------------------------------ openzfs-developer Archives: https://openzfs.topicbox.com/groups/developer/discussions/T1625245905c55186-M6d98b35cb0422dd6a7d9ab45 Powered by Topicbox: https://topicbox.com
