July 2017 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1156) Fwd: build-artifacts-on-demand marks CI +1

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1156?page=com.atlassian.jir... ] Barak Korren reassigned OVIRT-1156: ----------------------------------- Assignee: Barak Korren (was: infra) > Fwd: build-artifacts-on-demand marks CI +1 > ------------------------------------------ > > Key: OVIRT-1156 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1156 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: standard-ci > > Forwarding to Jira. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: 16 February 2017 at 15:02 > Subject: build-artifacts-on-demand marks CI +1 > To: infra <infra(a)ovirt.org> > Hi all, > I have a change [1] that currently fails some jenkins jobs, so it gets > -1 from it. After pushing patchset 4 (a mere rebase actually), I ran > build-artifacts-on-demand ("ci please build"), and it passed, and set > CI +1. Then I rebased again and again got -1 as expected. > IMO build-artifacts-on-demand should not set CI +1, it might be > misleading for the maintainer to think that all is good when in fact > CI failed. > [1] https://gerrit.ovirt.org/71590 > -- > Didi > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

7 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-1156) Fwd: build-artifacts-on-demand marks CI +1

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1156?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-1156: ------------------------------------- Created [a patch|https://gerrit.ovirt.org/78921] to fix this. [~danken(a)redhat.com] since you are the last person to report this, can you help +v the patch? I've applied it to the 'vdsm_master_build-artifacts-on-demand-*' jobs. > Fwd: build-artifacts-on-demand marks CI +1 > ------------------------------------------ > > Key: OVIRT-1156 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1156 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Forwarding to Jira. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: 16 February 2017 at 15:02 > Subject: build-artifacts-on-demand marks CI +1 > To: infra <infra(a)ovirt.org> > Hi all, > I have a change [1] that currently fails some jenkins jobs, so it gets > -1 from it. After pushing patchset 4 (a mere rebase actually), I ran > build-artifacts-on-demand ("ci please build"), and it passed, and set > CI +1. Then I rebased again and again got -1 as expected. > IMO build-artifacts-on-demand should not set CI +1, it might be > misleading for the maintainer to think that all is good when in fact > CI failed. > [1] https://gerrit.ovirt.org/71590 > -- > Didi > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

7 years, 4 months

1
0
0 / 0

Change 77768,30 (vdsm) failed system tests

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 77768,30 (vdsm) failed. However, this change seems not to be to root cause for failure. Change 78630,13 (vdsm) that this change depends on or is based on, was detected to cause testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 78630,13 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/77768/30 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/78630/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1025/

7 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-1499) false CI+1 on https://gerrit.ovirt.org/#/c/78910/1

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1499?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1499: -------------------------------- Resolution: Duplicate Status: Done (was: To Do) This is a duplicate of OVIRT-1156 > false CI+1 on https://gerrit.ovirt.org/#/c/78910/1 > -------------------------------------------------- > > Key: OVIRT-1499 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1499 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > I've posted https://gerrit.ovirt.org/#/c/78910/1 that included a > python style problem, and immediately asked for "ci please build". > http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/14766/ > justly gave me -1, but the later > http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-on-demand-el7-x8... > flipped it to +1. > This is wrong, and could have caused breakage of vdsm master. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

7 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-1156) Fwd: build-artifacts-on-demand marks CI +1

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1156?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1156: -------------------------------- Labels: standard-ci (was: sy) > Fwd: build-artifacts-on-demand marks CI +1 > ------------------------------------------ > > Key: OVIRT-1156 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1156 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Forwarding to Jira. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: 16 February 2017 at 15:02 > Subject: build-artifacts-on-demand marks CI +1 > To: infra <infra(a)ovirt.org> > Hi all, > I have a change [1] that currently fails some jenkins jobs, so it gets > -1 from it. After pushing patchset 4 (a mere rebase actually), I ran > build-artifacts-on-demand ("ci please build"), and it passed, and set > CI +1. Then I rebased again and again got -1 as expected. > IMO build-artifacts-on-demand should not set CI +1, it might be > misleading for the maintainer to think that all is good when in fact > CI failed. > [1] https://gerrit.ovirt.org/71590 > -- > Didi > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

7 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-1156) Fwd: build-artifacts-on-demand marks CI +1

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1156?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1156: -------------------------------- Labels: sy (was: ) > Fwd: build-artifacts-on-demand marks CI +1 > ------------------------------------------ > > Key: OVIRT-1156 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1156 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: sy > > Forwarding to Jira. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: 16 February 2017 at 15:02 > Subject: build-artifacts-on-demand marks CI +1 > To: infra <infra(a)ovirt.org> > Hi all, > I have a change [1] that currently fails some jenkins jobs, so it gets > -1 from it. After pushing patchset 4 (a mere rebase actually), I ran > build-artifacts-on-demand ("ci please build"), and it passed, and set > CI +1. Then I rebased again and again got -1 as expected. > IMO build-artifacts-on-demand should not set CI +1, it might be > misleading for the maintainer to think that all is good when in fact > CI failed. > [1] https://gerrit.ovirt.org/71590 > -- > Didi > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

7 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-1156) Fwd: build-artifacts-on-demand marks CI +1

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1156?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1156: -------------------------------- Component/s: oVirt CI > Fwd: build-artifacts-on-demand marks CI +1 > ------------------------------------------ > > Key: OVIRT-1156 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1156 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Forwarding to Jira. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: 16 February 2017 at 15:02 > Subject: build-artifacts-on-demand marks CI +1 > To: infra <infra(a)ovirt.org> > Hi all, > I have a change [1] that currently fails some jenkins jobs, so it gets > -1 from it. After pushing patchset 4 (a mere rebase actually), I ran > build-artifacts-on-demand ("ci please build"), and it passed, and set > CI +1. Then I rebased again and again got -1 as expected. > IMO build-artifacts-on-demand should not set CI +1, it might be > misleading for the maintainer to think that all is good when in fact > CI failed. > [1] https://gerrit.ovirt.org/71590 > -- > Didi > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

7 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-1499) false CI+1 on https://gerrit.ovirt.org/#/c/78910/1

by danken (oVirt JIRA)

danken created OVIRT-1499: ----------------------------- Summary: false CI+1 on https://gerrit.ovirt.org/#/c/78910/1 Key: OVIRT-1499 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1499 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: danken Assignee: infra I've posted https://gerrit.ovirt.org/#/c/78910/1 that included a python style problem, and immediately asked for "ci please build". http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/14766/ justly gave me -1, but the later http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-on-demand-el7-x8... flipped it to +1. This is wrong, and could have caused breakage of vdsm master. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

7 years, 4 months

1
0
0 / 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 176 - Failure!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_63_456482479.1498881608713 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artif... Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artif... Build Number: 176 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #176 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_63_456482479.1498881608713--

7 years, 4 months

1
3
0 / 0

Change 78630,13 (vdsm) failed system tests

by oVirt Jenkins

Change 78630,13 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/78630/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1023/

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra July 2017