Description of problem: Smoke fails for the following commits as it picks up the incorrect (commented out) BZ# to validate, (the following are examples) - https://review.gluster.org/c/glusterfs/+/20752/1//COMMIT_MSG - https://build.gluster.org/job/bugzilla-post/7377/console - https://review.gluster.org/c/glusterfs/+/20750/1//COMMIT_MSG - https://build.gluster.org/job/bugzilla-post/7374/console BTW, I think this happens for github issue reference as well, not finding an example ready at hand. Expected results: In the past lines starting with '>' were treated as comments in the commit message and ignored for parsing, I assume this is broken and needs correction. Additional info: There was a discussion in the devel list to drop this information, https://lists.gluster.org/pipermail/gluster-devel/2017-June/053140.html But, I guess that is stale for this conversation/bug. Posted it here, to state, if we are deliberately failing smoke due to these extra comments, then the bug possibly needs to be closed and we need to work on the bug #1428047 instead.
This is fixed for both github and bugzilla in https://github.com/gluster/glusterfs-patch-acceptance-tests/commit/ee993e8d6552bee753899702d305421e871b6114#diff-cade61baef1ca407b6f6a730bf4c6d34
*** Bug 1633487 has been marked as a duplicate of this bug. ***