https://bugzilla.redhat.com/show_bug.cgi?id=1618407

            Bug ID: 1618407
           Summary: Smoke jobs fail when commit messages have commented BZ
                    or other meta information
           Product: GlusterFS
           Version: mainline
         Component: project-infrastructure
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected], [email protected]



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.

-- 
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=0ZlpJhqfEn&a=cc_unsubscribe
_______________________________________________
Gluster-infra mailing list
[email protected]
https://lists.gluster.org/mailman/listinfo/gluster-infra

Reply via email to