There was a problem with our Jenkins instance. It is back in running order,
however failed builds need to be re-triggered.
More info on the root cause will be provided in the accompanying Jira
ticket:
https://ovirt-jira.atlassian.net/browse/OVIRT-1569
On Tue, Aug 1, 2017 at 5:33 PM, Nir Soffer <nsoffer(a)redhat.com> wrote:
Same on the fedora 25 job:
http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc25-
x86_64/10162/console
On Tue, Aug 1, 2017 at 6:31 PM Nir Soffer <nsoffer(a)redhat.com> wrote:
> Still running now, 39 minutes passed...
>
> On Tue, Aug 1, 2017 at 6:15 PM Nir Soffer <nsoffer(a)redhat.com> wrote:
>
>>
http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-
>> x86_64/16013/console
>>
>> The job failed as expected, the package is not available yet:
>>
>> *15:00:03* Error: Package: vdsm-4.20.2-1.git33dd5fe.el7.centos.x86_64
(/vdsm-4.20.2-1.git33dd5fe.el7.centos.x86_64)*15:00:03* Requires: sanlock >=
3.5.0-1*15:00:03* Installing: sanlock-3.4.0-1.el7.x86_64
(centos-base-el7)*15:00:03* sanlock = 3.4.0-1.el7*15:00:03* Error: Package:
vdsm-4.20.2-1.git33dd5fe.el7.centos.x86_64
(/vdsm-4.20.2-1.git33dd5fe.el7.centos.x86_64)*15:00:03* Requires: sanlock >=
3.5.0-1*15:00:03* Available: sanlock-3.4.0-1.el7.x86_64
(centos-base-el7)*15:00:03* sanlock = 3.4.0-1.el7*15:00:03* You could try
using --skip-broken to work around the problem*15:00:03* You could try running: rpm -Va
--nofiles --nodigest*15:00:03* Took 498 seconds*15:00:03*
===================================
>>
>>
>> But then it got stuck:
>>
>> *15:00:03* Build step 'Execute shell' marked build as failure*15:00:03* $
ssh-agent -k*15:00:03* unset SSH_AUTH_SOCK;*15:00:03* unset SSH_AGENT_PID;*15:00:03* echo
Agent pid 28320 killed;*15:00:03* [ssh-agent] Stopped.
>>
>>
>> And is still running now.
>>
>> Nir
>>
>
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
--
Regards,
Evgheni Dereveanchin