Description of problem:
Patch set 7 of https://review.gluster.org/#/c/20584/ had a report of "No Builds Executed" . Not sure what does that mean as there wasn't any voting back. Also on patch set 8, the smoke failed, link - https://build.gluster.org/job/devrpm-el7/10229/ .
Another observation what I have is even though the exit_on_failure was set to 'no' in run-tests.sh , however the regression didn't cover all the tests, link - https://build.gluster.org/job/centos7-regression/1965/
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The logs don't really indicate why patchset #7 did not trigger a smoke build. However, when patchset 8 was pushed, it triggered a message for patchset 7 to say "No Builds Exected". And then it went on to trigger the smoke builds. I will dig into Jenkins source code to figure out what happened.
Well, that was traced down to something wrong with Jenkins. My strong suspicion is after the latest Java update, Jenkins started to behave inconsistently. We eventually had to do a restart and this has been good ever since.