https://bugzilla.redhat.com/show_bug.cgi?id=1435254
Bug ID: 1435254
Summary: arbiter-mount.t is nuking everyone's regression tests
Product: GlusterFS
Version: mainline
Component: project-infrastructure
Assignee: b...@gluster.org
Reporter: j...@pl.atyp.us
CC: b...@gluster.org, gluster-infra@gluster.org
All of these seem to have failed spuriously because of rpc.statd not running.
Also, all of the ones I've looked at seemed to be on slave25.
https://build.gluster.org/job/centos6-regression/3727/console (tier)
https://build.gluster.org/job/centos6-regression/3728/console (glusterd)
https://build.gluster.org/job/centos6-regression/3732/console (glusterd)
https://build.gluster.org/job/centos6-regression/3732/console (readdir-ahead)
https://build.gluster.org/job/centos6-regression/3734/console (readdir-ahead)
https://build.gluster.org/job/centos6-regression/3735/console (afr)
https://build.gluster.org/job/centos6-regression/3736/console (glusterd)
So, is it an infrastructure issue, or related to the recent Ganesha mega-patch?
That's not clear. Assigning to infra initially because I can test that
hypothesis by disabling slave25 so the next test will run somewhere else. If
it fails there too, it's more likely to be an nfs issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=Bq4avCbPpD&a=cc_unsubscribe
_______________________________________________
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra
