Re: jenkins logs and ovirt-engine_master_upgrade-from-master_el7_merged

On Wed, Mar 30, 2016 at 10:22 AM, Sharon Naftaly <snaftaly(a)redhat.com&gt; wrote: > > On Wed, Mar 30, 2016 at 9:20 AM, Yedidyah Bar David <didi(a)redhat.com&gt; wrote: >> >> Hi all, >> >> On Tue, Mar 29, 2016 at 11:12 PM, Jenkins CI <gerrit2(a)gerrit.ovirt.org&gt; >> 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_... >> > : 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(a)redhat.com infra(a)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_mer... I know, the patches for 3.6 are pending review. Thanks, -- Didi