jenkins logs and ovirt-engine_master_upgrade-from-master_el7_merged
Hi all, On Tue, Mar 29, 2016 at 11:12 PM, Jenkins CI <gerrit2@gerrit.ovirt.org> wrote:
Jenkins CI has posted comments on this change.
Change subject: packaging: spec: Fix deps for ovirt-engine-tools-backup ......................................................................
Patch Set 2:
Build Failed
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_mer... : FAILURE
This failed due to [1]. Above run 2500 contained the fix, but still failed. Why? Because it started from a broken build. The fix only fixes upgrades from good builds to good builds. I tried to follow the console logs of various runs of this job and have some questions: 1. How do we decide what version to upgrade *from*? 2. I suspect that we pick the last "good" version, with some definition of good, but by the time I am looking at this, there are already newer runs that succeeded, but all those before 2500 failed. Can't see in the web interface older non-failed ones. 3. Also searched my mail and could not find a report. When do we send email? To whom? Is there an archive somewhere? Not that important, now that all is fixed. Asking mainly for my own understanding. [1] https://bugzilla.redhat.com/1321249
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged... : FAILURE
http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_merged/15370... : SUCCESS
http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-el7-x86_64/212... : SUCCESS
http://jenkins.ovirt.org/job/ovirt-engine_master_unit-tests_merged/15408/ : SUCCESS
http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc23-x86_64/17... : SUCCESS
-- To view, visit https://gerrit.ovirt.org/55287 To unsubscribe, visit https://gerrit.ovirt.org/settings
Gerrit-MessageType: comment Gerrit-Change-Id: I2772037157f2f1ba77b3be96c6375558fe3d6582 Gerrit-PatchSet: 2 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Yedidyah Bar David <didi@redhat.com> Gerrit-Reviewer: Jenkins CI Gerrit-Reviewer: Sandro Bonazzola <sbonazzo@redhat.com> Gerrit-Reviewer: Yedidyah Bar David <didi@redhat.com> Gerrit-Reviewer: gerrit-hooks <automation@ovirt.org> Gerrit-HasComments: No
-- Didi
On Wed, Mar 30, 2016 at 9:20 AM, Yedidyah Bar David <didi@redhat.com> wrote:
Hi all,
On Tue, Mar 29, 2016 at 11:12 PM, Jenkins CI <gerrit2@gerrit.ovirt.org> wrote:
Jenkins CI has posted comments on this change.
Change subject: packaging: spec: Fix deps for ovirt-engine-tools-backup ......................................................................
Patch Set 2:
Build Failed
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_mer... : FAILURE
This failed due to [1].
Above run 2500 contained the fix, but still failed. Why? Because it started from a broken build. The fix only fixes upgrades from good builds to good builds.
I tried to follow the console logs of various runs of this job and have some questions:
1. How do we decide what version to upgrade *from*?
The repos we use to upgrade 'from' are: http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/ and http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/el7/ Afaik the latest version is taken from there (looking at the date modified I see that yesterday it was indeed ovirt-engine-4.0.0-0.0.master.20160328161540.gitecdf3dc.el7.centos.noarch.rpm)
2. I suspect that we pick the last "good" version, with some definition of good, but by the time I am looking at this, there are already newer runs that succeeded, but all those before 2500 failed. Can't see in the web interface older non-failed ones.
3. Also searched my mail and could not find a report. When do we send email? To whom? Is there an archive somewhere?
In the logs of build #2500 I see Sending email to: didi@redhat.com infra@ovirt.org
Not that important, now that all is fixed. Asking mainly for my own understanding.
By the way, I see that the 3.6->master upgrade fails on a similar issue: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged...
[1] https://bugzilla.redhat.com/1321249
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged... : FAILURE
http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_merged/15370... : SUCCESS
http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-el7-x86_64/212... : SUCCESS
http://jenkins.ovirt.org/job/ovirt-engine_master_unit-tests_merged/15408/ : SUCCESS
http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc23-x86_64/17... : SUCCESS
-- To view, visit https://gerrit.ovirt.org/55287 To unsubscribe, visit https://gerrit.ovirt.org/settings
Gerrit-MessageType: comment Gerrit-Change-Id: I2772037157f2f1ba77b3be96c6375558fe3d6582 Gerrit-PatchSet: 2 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Yedidyah Bar David <didi@redhat.com> Gerrit-Reviewer: Jenkins CI Gerrit-Reviewer: Sandro Bonazzola <sbonazzo@redhat.com> Gerrit-Reviewer: Yedidyah Bar David <didi@redhat.com> Gerrit-Reviewer: gerrit-hooks <automation@ovirt.org> Gerrit-HasComments: No
-- Didi _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On Wed, Mar 30, 2016 at 10:22 AM, Sharon Naftaly <snaftaly@redhat.com> wrote:
On Wed, Mar 30, 2016 at 9:20 AM, Yedidyah Bar David <didi@redhat.com> wrote:
Hi all,
On Tue, Mar 29, 2016 at 11:12 PM, Jenkins CI <gerrit2@gerrit.ovirt.org> wrote:
Jenkins CI has posted comments on this change.
Change subject: packaging: spec: Fix deps for ovirt-engine-tools-backup ......................................................................
Patch Set 2:
Build Failed
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_mer... : FAILURE
This failed due to [1].
Above run 2500 contained the fix, but still failed. Why? Because it started from a broken build. The fix only fixes upgrades from good builds to good builds.
I tried to follow the console logs of various runs of this job and have some questions:
1. How do we decide what version to upgrade *from*?
The repos we use to upgrade 'from' are: http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/ and http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/el7/ Afaik the latest version is taken from there (looking at the date modified I see that yesterday it was indeed ovirt-engine-4.0.0-0.0.master.20160328161540.gitecdf3dc.el7.centos.noarch.rpm)
OK, makes sense.
2. I suspect that we pick the last "good" version, with some definition of good, but by the time I am looking at this, there are already newer runs that succeeded, but all those before 2500 failed. Can't see in the web interface older non-failed ones.
3. Also searched my mail and could not find a report. When do we send email? To whom? Is there an archive somewhere?
In the logs of build #2500 I see
Sending email to: didi@redhat.com infra@ovirt.org
I meant - do we send also "back to normal" mails? I see some in infra's archives, but not for this job.
Not that important, now that all is fixed. Asking mainly for my own understanding.
By the way, I see that the 3.6->master upgrade fails on a similar issue: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged...
I know, the patches for 3.6 are pending review. Thanks, -- Didi
On Wed, Mar 30, 2016 at 10:49 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Wed, Mar 30, 2016 at 10:22 AM, Sharon Naftaly <snaftaly@redhat.com> wrote:
On Wed, Mar 30, 2016 at 9:20 AM, Yedidyah Bar David <didi@redhat.com>
wrote:
Hi all,
On Tue, Mar 29, 2016 at 11:12 PM, Jenkins CI <gerrit2@gerrit.ovirt.org> wrote:
Jenkins CI has posted comments on this change.
Change subject: packaging: spec: Fix deps for
ovirt-engine-tools-backup
......................................................................
Patch Set 2:
Build Failed
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_mer...
: FAILURE
This failed due to [1].
Above run 2500 contained the fix, but still failed. Why? Because it started from a broken build. The fix only fixes upgrades from good builds to good builds.
I tried to follow the console logs of various runs of this job and have some questions:
1. How do we decide what version to upgrade *from*?
The repos we use to upgrade 'from' are: http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/ and http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/el7/ Afaik the latest version is taken from there (looking at the date modified I see that yesterday it was indeed
ovirt-engine-4.0.0-0.0.master.20160328161540.gitecdf3dc.el7.centos.noarch.rpm)
OK, makes sense.
2. I suspect that we pick the last "good" version, with some definition
of
good, but by the time I am looking at this, there are already newer runs that succeeded, but all those before 2500 failed. Can't see in the web interface older non-failed ones.
3. Also searched my mail and could not find a report. When do we send email? To whom? Is there an archive somewhere?
In the logs of build #2500 I see
Sending email to: didi@redhat.com infra@ovirt.org
I meant - do we send also "back to normal" mails? I see some in infra's archives, but not for this job.
You're right - I'll add it.
Not that important, now that all is fixed. Asking mainly for my own understanding.
By the way, I see that the 3.6->master upgrade fails on a similar issue:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged...
I know, the patches for 3.6 are pending review.
Thanks, -- Didi
participants (2)
-
Sharon Naftaly -
Yedidyah Bar David