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 <[email protected]> wrote: > > > On Thu, May 19, 2016 at 4:26 PM, Tal Nisan <[email protected]> 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-engine_master_upgrade-from-master_el7_merged/310/ >> : FAILURE >> >> >> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/307/ >> : FAILURE >> > > Yes, but those are executed only after patch is merged, check-patch jobs > are return SUCCESS if when build failed, David is working on that. > > >> >> On Thu, May 19, 2016 at 5:22 PM, David Caro <[email protected]> wrote: >> >>> On 05/19 16:20, Martin Perina wrote: >>> > On Thu, May 19, 2016 at 4:15 PM, David Caro <[email protected]> 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 jobs, the build itself >>> failed, >>> > > but >>> > > > build jobs are marked as SUCCESSFULL. >>> > > > So it seems we have a bug in those jobs!!! >>> > > >>> > > >>> > > We will need a bit more info on which project/jenkins job/build, >>> etc, by >>> > > the >>> > > email I can't extract the project that failed >>> > > >>> > >>> > Sorry, here is the problematic patch: >>> https://gerrit.ovirt.org/#/c/57052/ >>> > >>> > The problematic patch is build on patch set 20. It's marked as >>> successfull, >>> > although engine build failed: >>> > >>> > >>> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/1250/console >>> > >>> > >>> > Anyway, we are preparing reverting patch ... >>> >>> >>> I see, the issue was introduced by me in the mock_runner.sh script, will >>> send a >>> patch right away >>> >>> > >>> > Sorry for the issue. >>> > >>> > Martin >>> > >>> > >>> > >>> > > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > > On Thu, May 19, 2016 at 3:53 PM, Tal Nisan <[email protected]> >>> wrote: >>> > > > >>> > > > > This commit broke the build, missing KernelEnv. >>> > > > > Normally I'd revert but since it's feature freeze I'm more >>> forgiving :) >>> > > > > Please either revert or send a fix asap. >>> > > > > >>> > > > > Thanks. >>> > > > > >>> > > > > >>> > > >>> > > > _______________________________________________ >>> > > > Infra mailing list >>> > > > [email protected] >>> > > > http://lists.ovirt.org/mailman/listinfo/infra >>> > > >>> > > >>> > > -- >>> > > David Caro >>> > > >>> > > Red Hat S.L. >>> > > Continuous Integration Engineer - EMEA ENG Virtualization R&D >>> > > >>> > > Tel.: +420 532 294 605 >>> > > Email: [email protected] >>> > > IRC: dcaro|dcaroest@{freenode|oftc|redhat} >>> > > Web: www.redhat.com >>> > > RHT Global #: 82-62605 >>> > > >>> >>> -- >>> David Caro >>> >>> Red Hat S.L. >>> Continuous Integration Engineer - EMEA ENG Virtualization R&D >>> >>> Tel.: +420 532 294 605 >>> Email: [email protected] >>> IRC: dcaro|dcaroest@{freenode|oftc|redhat} >>> Web: www.redhat.com >>> RHT Global #: 82-62605 >>> >> >> >
_______________________________________________ Infra mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/infra
