On Tue, Apr 5, 2016 at 4:24 PM, Kaushal M wrote:
>
> On 5 Apr 2016 3:43 p.m., "Kaushal M" wrote:
>>
>> So gerrit voting seems to be working again. It required all the jobs
>> to have the same trigger configuration.
>>
>> Smoke vote was given for [1] a test change that I posted for review.
>> Now
On 5 Apr 2016 3:43 p.m., "Kaushal M" wrote:
>
> So gerrit voting seems to be working again. It required all the jobs
> to have the same trigger configuration.
>
> Smoke vote was given for [1] a test change that I posted for review.
> Now just need to check if it works for changes which already hav
So gerrit voting seems to be working again. It required all the jobs
to have the same trigger configuration.
Smoke vote was given for [1] a test change that I posted for review.
Now just need to check if it works for changes which already have
regressions run on them.
I'll be following [2] to see
On Tue, Apr 5, 2016 at 12:39 PM, Kaushal M wrote:
> On Tue, Apr 5, 2016 at 11:26 AM, Kaushal M wrote:
>> On Tue, Apr 5, 2016 at 11:10 AM, Atin Mukherjee wrote:
>>>
>>>
>>> On 04/05/2016 11:06 AM, Kaushal M wrote:
I did some changes so that all smoke jobs (linux, *bsd smoke jobs,
devrpm
On Tue, Apr 5, 2016 at 11:26 AM, Kaushal M wrote:
> On Tue, Apr 5, 2016 at 11:10 AM, Atin Mukherjee wrote:
>>
>>
>> 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 c
On Tue, Apr 5, 2016 at 11:10 AM, Atin Mukherjee wrote:
>
>
> 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
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 al
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
