That zloop failure looks similar to what happened the previous run that also failed zloop; see [here](http://jenkins.open-zfs.org/blue/organizations/jenkins/openzfs%2Fopenzfs/detail/PR-494/6/pipeline/211). There _might_ be some information that can be gathered from the zloop files, which can be downloaded [here](http://jenkins.open-zfs.org/job/openzfs/job/openzfs/job/PR-494/9/artifact/run-zloop-results.tar.xz). If there's nothing useful in there, can you try running zloop locally to see if you can trigger anything abnormal?
I have a hunch that zloop is getting "stuck", and then is killed by the Jenkins time limit after it fails to return. It's supposed to run for only 1.5 hours, and then has a 2 hour time limit enforce by Jenkins. In this case, it looks like the underlying ztest process was only supposed to run for 56 seconds: ``` 11/29 19:31:01 ztest -VVVVV -m 2 -r 0 -R 1 -v 2 -a 9 -T 56 -P 23 -s 128m -f /var/tmp/test_results ``` but it seems as though it didn't return after 2 hours (hence hitting the time limit, and being killed). -- 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/494#issuecomment-348234172 ------------------------------------------ openzfs-developer Archives: https://openzfs.topicbox.com/groups/developer/discussions/T34088d4e3e9cd4f5-M01e38a9c20f7e632e465491d Powered by Topicbox: https://topicbox.com
