### Logwatch 7.3.6 (05/19/07)
Processing Initiated: Fri Nov 20 03:34:06 2015
Date Range Processed: yesterday
( 2015-Nov-19 )
Period is day.
Detail Level of Output: 0
Hello All.
Please note that we are going to upgrade Jenkins today. Due to this it is
put into shutdown mode and thus it is not executing jobs till the update is
done.
We aim at making this procedure as smoothly as possible, but we face
network issues right now and thus this looks like we will hav
Hello All.
Jenkins has been upgraded. We are now watching for any side effects left.
Please feel free to retrigger your jobs in case they are missed.
Shall you see any strange problem to appear, please drop us a not to infra.
Anton.
On Fri, Nov 20, 2015 at 12:26 PM, Anton Marchukov
wrote:
>
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/879/
Build Number: 879
Build Status: Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/48447
Hello Einav.
Yes those are network issues we saw today midday. Does not look like
upgrade related.
Anton.
On Fri, Nov 20, 2015 at 4:41 PM, Einav Cohen wrote:
> both of these seem shaky (might not be related to the upgrade):
>
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc22
both of these seem shaky (might not be related to the upgrade):
http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc22-x86_64/ [1]
http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc23-x86_64/ [2]
Thanks,
Einav
[1] from #569 console output:
...
14:08:21 Downloading:
Hi infra,
This failure is not a valid reason to mark the patch with -1.
00:15:09.614 ERROR: Failed to umount
/var/lib/mock/epel-6-x86_64-d496d3daa673001f46dbbd9addf9ba1b/root/home/jenkins/workspace/ovirt-engine_3.6_check-patch-el6-x86_64/ovirt-engine.
00:15:09.614 + failed=true
See
http://jenk
There was on slave that still carried failures from the latest cleanup issue
last week, it's now solved and should not happen again.
Thanks for the suggestion.
On 11/20 20:22, Nir Soffer wrote:
> Hi infra,
>
> This failure is not a valid reason to mark the patch with -1.
>
> 00:15:09.614 ERROR
On Fri, Nov 20, 2015 at 9:25 PM, David Caro wrote:
>
> There was on slave that still carried failures from the latest cleanup issue
> last week, it's now solved and should not happen again.
Thanks for the quick response David!
Unfortunately, It just happened again :-)
http://jenkins.ovirt.org/j
On 11/20 22:59, Nir Soffer wrote:
> On Fri, Nov 20, 2015 at 9:25 PM, David Caro wrote:
> >
> > There was on slave that still carried failures from the latest cleanup issue
> > last week, it's now solved and should not happen again.
>
> Thanks for the quick response David!
>
> Unfortunately, It
Thanks David, I will report failures as usual.
Nir
On Fri, Nov 20, 2015 at 11:44 PM, David Caro wrote:
>
> On 11/20 22:59, Nir Soffer wrote:
>> On Fri, Nov 20, 2015 at 9:25 PM, David Caro wrote:
>> >
>> > There was on slave that still carried failures from the latest cleanup
>> > issue
>> > la
We have now 39 members - but only 13 are public.
To make yourself public, visit
https://github.com/orgs/oVirt/people
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
12 matches
Mail list logo