https://bugzilla.redhat.com/show_bug.cgi?id=1493408
Bug ID: 1493408
Summary: abort regression jobs after a period of inactivity
rather than a hard timeout of 360 minutes
Product: GlusterFS
Version: mainline
Component: project-infrastructure
Assignee: b...@gluster.org
Reporter: mchan...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
Description of problem:
Sometimes regression jobs hang earlier than 360 minutes.
Sometimes the regressions just run slower.
Expected results:
It would help to abort regression jobs earlier than 360 minutes and reboot the
node to make way for other jobs if there has been 15 minutes of inactivity on
the STDOUT.
This will help to abort hung jobs earlier than wasting time.
For slow running regression jobs, this would help to continue and complete the
regression run than aborting the job and running it again for 360 minutes.
--
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=RdZliWJ3qJ&a=cc_unsubscribe
_______________________________________________
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra
