[Gluster-infra] [Gluster-devel] Smoke results voting
amukherj at redhat.com
Tue Apr 5 05:40:07 UTC 2016
On 04/05/2016 11:06 AM, Kaushal M wrote:
> 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.
Is there a way that this doesn't impact the merging as until we get all
the positive votes, web interface doesn't provide a submit button.
> On Mon, Apr 4, 2016 at 10:39 PM, Prasanna Kalever <pkalever at redhat.com> wrote:
>> On Mon, Apr 4, 2016 at 9:58 PM, Atin Mukherjee
>> <atin.mukherjee83 at gmail.com> wrote:
>>> Did anyone notice that for few of the patches smoke results are not voted
>>> http://review.gluster.org/#/c/13869 is one of them.
>> 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 ...
>>> Sent from one plus one
>>> Gluster-infra mailing list
>>> Gluster-infra at gluster.org
>> Gluster-devel mailing list
>> Gluster-devel at gluster.org
> Gluster-devel mailing list
> Gluster-devel at gluster.org
More information about the Gluster-infra