<div dir="ltr"><br><div><div class="gmail_extra"><div class="gmail_quote">On Wed, Mar 30, 2016 at 10:49 AM, Yedidyah Bar David <span dir="ltr"><<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, Mar 30, 2016 at 10:22 AM, Sharon Naftaly <<a href="mailto:snaftaly@redhat.com">snaftaly@redhat.com</a>> wrote:<br>
><br>
> On Wed, Mar 30, 2016 at 9:20 AM, Yedidyah Bar David <<a href="mailto:didi@redhat.com">didi@redhat.com</a>> wrote:<br>
>><br>
>> Hi all,<br>
>><br>
>> On Tue, Mar 29, 2016 at 11:12 PM, Jenkins CI <<a href="mailto:gerrit2@gerrit.ovirt.org">gerrit2@gerrit.ovirt.org</a>><br>
>> wrote:<br>
>> > Jenkins CI has posted comments on this change.<br>
>> ><br>
>> > Change subject: packaging: spec: Fix deps for ovirt-engine-tools-backup<br>
>> > ......................................................................<br>
>> ><br>
>> ><br>
>> > Patch Set 2:<br>
>> ><br>
>> > Build Failed<br>
>> ><br>
>> ><br>
>> > <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/2500/" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/2500/</a><br>
>> > : FAILURE<br>
>><br>
>> This failed due to [1].<br>
>><br>
>> Above run 2500 contained the fix, but still failed. Why? Because it<br>
>> started from a broken build. The fix only fixes upgrades from good<br>
>> builds to good builds.<br>
>><br>
>> I tried to follow the console logs of various runs of this job and<br>
>> have some questions:<br>
>><br>
>> 1. How do we decide what version to upgrade *from*?<br>
><br>
> The repos we use to upgrade 'from' are:<br>
> <a href="http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/" rel="noreferrer" target="_blank">http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/</a> and<br>
> <a href="http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/el7/" rel="noreferrer" target="_blank">http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/el7/</a><br>
> Afaik the latest version is taken from there (looking at the date modified I<br>
> see that yesterday it was indeed<br>
> ovirt-engine-4.0.0-0.0.master.20160328161540.gitecdf3dc.el7.centos.noarch.rpm)<br>
<br>
</div></div>OK, makes sense.<br>
<span class=""><br>
>><br>
>><br>
>> 2. I suspect that we pick the last "good" version, with some definition of<br>
>> good,<br>
>> but by the time I am looking at this, there are already newer runs<br>
>> that succeeded, but all those before 2500 failed. Can't see in the web<br>
>> interface older non-failed ones.<br>
>><br>
>> 3. Also searched my mail and could not find a report. When do we send<br>
>> email? To whom? Is there an archive somewhere?<br>
><br>
><br>
> In the logs of build #2500 I see<br>
><br>
> Sending email to: <a href="mailto:didi@redhat.com">didi@redhat.com</a> <a href="mailto:infra@ovirt.org">infra@ovirt.org</a><br>
<br>
</span>I meant - do we send also "back to normal" mails? I see some in infra's<br>
archives, but not for this job.<br></blockquote><div>You're right - I'll add it.<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
>><br>
>><br>
>> Not that important, now that all is fixed. Asking mainly for my own<br>
>> understanding.<br>
>><br>
><br>
> By the way, I see that the 3.6->master upgrade fails on a similar issue:<br>
> <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/2390/console" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/2390/console</a><br>
<br>
</span>I know, the patches for 3.6 are pending review.<br>
<br>
Thanks,<br>
<span class="HOEnZb"><font color="#888888">--<br>
Didi<br>
</font></span></blockquote></div><br></div></div></div>