Oh I see now what you are talking about, indeed in patchset 20 jobs were
marked as successful even though the actually failed, a bug indeed
On Thu, May 19, 2016 at 5:33 PM, Martin Perina wrote:
>
>
> On Thu, May 19, 2016 at 4:26 PM, Tal Nisan wrote:
>
>> No need, already reverted once I've read
On Thu, May 19, 2016 at 4:26 PM, Tal Nisan wrote:
> No need, already reverted once I've read you message, had it reverted and
> verified so I could keep working on the branch -
> https://gerrit.ovirt.org/#/c/57742/
> BTW, both jobs ended with a failure:
>
>
> http://jenkins.ovirt.org/job/ovirt-en
No need, already reverted once I've read you message, had it reverted and
verified so I could keep working on the branch -
https://gerrit.ovirt.org/#/c/57742/
BTW, both jobs ended with a failure:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/310/
: FAILURE
http:/
On 05/19 16:20, Martin Perina wrote:
> On Thu, May 19, 2016 at 4:15 PM, David Caro wrote:
>
> > On 05/19 16:14, Martin Perina wrote:
> > > Hi,
> > >
> > > so I probably found the issue why this broke the build. I have checked
> > the
> > > CI before merging and it was OK,
> > > see CI+1 on patch
Hi,
so I probably found the issue why this broke the build. I have checked the
CI before merging and it was OK,
see CI+1 on patch set 20.
Now looking at console outputs of those jobs, the build itself failed, but
build jobs are marked as SUCCESSFULL.
So it seems we have a bug in those jobs!!!
On Thu, May 19, 2016 at 4:15 PM, David Caro wrote:
> On 05/19 16:14, Martin Perina wrote:
> > Hi,
> >
> > so I probably found the issue why this broke the build. I have checked
> the
> > CI before merging and it was OK,
> > see CI+1 on patch set 20.
> >
> > Now looking at console outputs of those
On 05/19 16:14, Martin Perina wrote:
> Hi,
>
> so I probably found the issue why this broke the build. I have checked the
> CI before merging and it was OK,
> see CI+1 on patch set 20.
>
> Now looking at console outputs of those jobs, the build itself failed, but
> build jobs are marked as SUCCES
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/308/
Build Number: 308
Build Status: Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/57719
--
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/311/
Build Number: 311
Build Status: Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/57719
Hi,
Did and Sandro are working on that
Thanks
Gil
On Thu, May 19, 2016 at 4:58 PM, Martin Perina wrote:
> Hi,
>
> could you please take a look why upgrade jobs are failing?
>
> Thanks
>
> Martin
>
>
> On Thu, May 19, 2016 at 3:47 PM, Jenkins CI
> wrote:
>
>> Jenkins CI has posted comments on
Hi,
could you please take a look why upgrade jobs are failing?
Thanks
Martin
On Thu, May 19, 2016 at 3:47 PM, Jenkins CI
wrote:
> Jenkins CI has posted comments on this change.
>
> Change subject: core: Kernel cmdline - host deploy
> ..
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/307/
Build Number: 307
Build Status: Still Failing
Triggered By: Retriggered by user gshinar for Gerrit:
https://gerrit.ovi
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/306/
Build Number: 306
Build Status: Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/57052
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/310/
Build Number: 310
Build Status: Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/57052
-
14 matches
Mail list logo
