As both Shyam & I are running multiple flavours of manually triggered regression jobs (lcov, centos-7, brick-mux) on top of https://review.gluster.org/#/c/glusterfs/+/20637/ , we'd need to occupy most the builders.
I have currently run out of builders to trigger some of the runs and have observed one of the patches occupying it and the patch doesn't come under stabilization bucket. Where there's no harm in keeping your patch up to date with the regression, but given the most critical part is to make upstream regression suits back to green asap, I've no choice but to kill such jobs. However I will add a note to the respective patches before killing such jobs.
Inconvenience regretted.
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
