I did some changes so that all smoke jobs (linux, *bsd smoke jobs, devrpm jobs etc) are triggered for `recheck smoke`. The collated results are being reported back and the 'Smoke' flag is being set. But sometimes, if regression jobs have been already run on the patchset, jenkins is collating those results as well. When this happens, a '-Verified' flag is being set. Jenkins and its gerrit plugin collate results for jobs launched by the same event. The regression and smoke jobs should be triggered for different events, but for some reason jenkins is assuming that they're being triggered by the same event and collating all of them together. I need some time to figure out why this is happening, and fix it. ~kaushal On Mon, Apr 4, 2016 at 10:39 PM, Prasanna Kalever <pkalever@xxxxxxxxxx> wrote: > On Mon, Apr 4, 2016 at 9:58 PM, Atin Mukherjee > <atin.mukherjee83@xxxxxxxxx> wrote: >> Did anyone notice that for few of the patches smoke results are not voted >> back? >> >> http://review.gluster.org/#/c/13869 is one of them. > > +1 > > Here is another one http://review.gluster.org/#/c/11083/ > I have also re-triggered it with "recheck smoke", after which > it return success "http://build.gluster.org/job/smoke/26373/ : SUCCESS" > > but again failed to report back ... > > -- > Prasanna > > >> >> -Atin >> Sent from one plus one >> >> >> _______________________________________________ >> Gluster-infra mailing list >> Gluster-infra@xxxxxxxxxxx >> http://www.gluster.org/mailman/listinfo/gluster-infra > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-devel _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
