Le mercredi 11 mai 2016 à 15:39 +0200, Niels de Vos a écrit : > Could someone look into this busy loop? > https://paste.fedoraproject.org/365207/29732171/raw/ > > This was happening in a regression-test burn-in run, occupying a Jenkins > slave for 2+ days: > https://build.gluster.org/job/regression-test-burn-in/936/ > (run with commit f0ade919006b2581ae192f997a8ae5bacc2892af from master) > > A coredump of the mount process is available from here: > http://slave20.cloud.gluster.org/archived_builds/crash.tar.gz > > Thanks misc for reporting and gathering the debugging info. There is the same problem on slave0 https://build.gluster.org/job/regression-test-burn-in/931/ run with abd27041ebcb3c6ee897ad253fc248e3bb1823e6 Core on http://slave0.cloud.gluster.org/archived_builds/crash.tar.gz I am rebooting both builders in 5 minutes. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
