not sure, the results are created from the src code, and if the same job
checksout diff patches to the same place that can create the fp errors we see
now..
deleting the results will just mean they will be created again the same...
On Jan 3, 2014 9:42 AM, Itamar Heim wrote:
>
> On 01/03/2014 08
On 01/03/2014 08:58 AM, Eyal Edri wrote:
The obvious is to enable wipe workspace per run, but i fear that will be
add much more run time per patch and that jenkins won't be able to handle the
queue of jobs, but it's worth a try.
i will enable it for now, and we'll monitor the queue size.
I don
The obvious is to enable wipe workspace per run, but i fear that will be
add much more run time per patch and that jenkins won't be able to handle the
queue of jobs, but it's worth a try.
i will enable it for now, and we'll monitor the queue size.
eyal.
- Original Message -
> From: "Y
Project: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/
Build: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/93061/
Build Number: 93061
Build Status: Fixed
Triggered By: Started by timer
-
Changes Since Last Success:
---
Project: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/
Build: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/93060/
Build Number: 93060
Build Status: Failure
Triggered By: Started by timer
-
Changes Since Last Success:
-
Project: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/
Build: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/93051/
Build Number: 93051
Build Status: Fixed
Triggered By: Started by timer
-
Changes Since Last Success:
---
Project: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/
Build: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/93050/
Build Number: 93050
Build Status: Failure
Triggered By: Started by timer
-
Changes Since Last Success:
-
Project: http://jenkins.ovirt.org/job/ovirt_engine_upgrade_params/
Build: http://jenkins.ovirt.org/job/ovirt_engine_upgrade_params/63/
Build Number: 63
Build Status: Still Failing
Triggered By: Started by timer
-
Changes Since Last Success:
---
Project: http://jenkins.ovirt.org/job/check_disk_space_on_jenkins_slaves/
Build: http://jenkins.ovirt.org/job/check_disk_space_on_jenkins_slaves/540/
Build Number: 540
Build Status: Failure
Triggered By: Started by timer
-
Changes Since Last Success:
-
Project:
http://jenkins.ovirt.org/job/check_disk_space_on_jenkins_slaves/./label=centos64/
Build:
http://jenkins.ovirt.org/job/check_disk_space_on_jenkins_slaves/./label=centos64/540/
Build Number: 540
Build Status: Failure
Triggered By: Started by upstream project "check_disk_space_on_jenkins
Sending logs to a host far far away
Processing logfile /var/log/httpd/access_log-20140101.gz
Pseudo-terminal will not be allocated because stdin is not a terminal.
Address 31.15.26.3 maps to lists.ovirt.org, but this does not map back to the
address - POSSIBLE BREAK-IN ATTEMPT!
Last failed login:
On Thu, 2 Jan 2014, Dave Neary wrote:
> I am not sure who manages ovirt.org's DNS records, but if we can add a
> PTR record for 2600:3c01::f03c:91ff:fe93:4b0d and that solved the issue,
> that would be great.
>
> Who can do this?
ssh into the host, from an ipv6 capable unit, and view its
ipv4 a
Since Linode is owner of the reverse DNS zone, whoever has access to the
linode control panel.
On Thu, Jan 02, 2014 at 08:41:22PM +0100, Dave Neary wrote:
> Thanks for the hints Russ!
>
> I am not sure who manages ovirt.org's DNS records, but if we can add a
> PTR record for 2600:3c01::f03c:91ff:
Thanks for the hints Russ!
I am not sure who manages ovirt.org's DNS records, but if we can add a
PTR record for 2600:3c01::f03c:91ff:fe93:4b0d and that solved the issue,
that would be great.
Who can do this?
Thanks,
Dave.
On 01/02/2014 07:08 PM, R P Herrold wrote:
> On Thu, 2 Jan 2014, Dave Ne
On Thu, 2 Jan 2014, Dave Neary wrote:
> I looked up lists.ovirt.org, linode01.ovirt.org and ovirt.org on
> SenderBase, and all have a good reputation... anyone more familiar with
> mail spam handling who can intervene/investigate?
> > "said: 550 Connections from the host Unknown
> > (2600:3c
ok,
sandro - can we update the ovirt-testing repo with the latest pkg?
or remove the offending one?
eyal.
- Original Message -
> From: "Dan Kenigsberg"
> To: "Eyal Edri"
> Cc: "Ewoud Kohl van Wijngaarden" ,
> infra@ovirt.org
> Sent: Thursday, January 2, 2014 4:50:45 PM
> Subject: Re:
On Wed, Jan 01, 2014 at 02:10:54PM -0500, Eyal Edri wrote:
> the problem is that one vdsm jobs needs python-cpopen (like unit tests),
> while another job (like vdsm install sanity) fails on it cause of conflict
> with vdsm-python-cpopen,
> so puppet does what it should like all other pkg.
>
> wha
Hi,
I looked up lists.ovirt.org, linode01.ovirt.org and ovirt.org on
SenderBase, and all have a good reputation... anyone more familiar with
mail spam handling who can intervene/investigate?
Thanks,
Dave.
On 12/26/2013 10:49 AM, Itamar Heim wrote:
> our email are being blocked on:
> "said: 550 C
On Wed, Jan 01, 2014 at 02:10:54PM -0500, Eyal Edri wrote:
> the problem is that one vdsm jobs needs python-cpopen (like unit tests),
> while another job (like vdsm install sanity) fails on it cause of conflict
> with vdsm-python-cpopen,
> so puppet does what it should like all other pkg.
>
> wha
On 01/02/2014 09:24 AM, Eyal Edri wrote:
fyi,
patch http://gerrit.ovirt.org/#/c/22614/ has compilation errors and currently
fails most of jenkins jobs.
the reason for jenkins not failing the patch is the short time between the new
patchset #3 was added (rebased)
to the actual merge time, so je
### Logwatch 7.3.6 (05/19/07)
Processing Initiated: Thu Jan 2 03:08:06 2014
Date Range Processed: yesterday
( 2014-Jan-01 )
Period is day.
Detail Level of Output: 0
21 matches
Mail list logo
