https://bugzilla.redhat.com/show_bug.cgi?id=1366106
Bug ID: 1366106 Summary: Regression jobs vote on the exact patchset Product: GlusterFS Version: mainline Component: project-infrastructure Keywords: Triaged Assignee: nig...@redhat.com Reporter: nig...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org The centos regression and netbsd regression vote on an exact patchset number. This works okay 90% of the cases. But we run into ad edge case: 1. Patchset 1 has Verified +1 added triggering regression jobs. 2. Edit commit message, creating Patchset 2. 3. Jenkins reports success/failures on Patchset 1. Since it's to an older commit, the patch ends up not being counted. We need to figure out a way to ensure it's counted *if* the changes were superficial or have the discipline to not change commit messages until regression jobs have reported back. -- 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=7kMdfzlx3u&a=cc_unsubscribe _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra