Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Reply-To: <gavin@16degrees.com.au>
From: "Gavin McDonald" <gavin@16degrees.com.au>
To: <builds@apache.org>
References: <4FC64784.5030306@oracle.com>
In-Reply-To: <4FC64784.5030306@oracle.com>
Subject: RE: [Jenkins] poor handling of offline slaves
Date: Fri, 1 Jun 2012 13:16:31 +0930
Organization: 16 degrees complete web solutions
Message-ID: <15ef101cd3fa9$22613030$67239090$@16degrees.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-au
Thread-Index: AQHRodg73A3TB/3VODB5P1IA5scQvZbcDR5Q


> -----Original Message-----
> From: Kristian Waagan [mailto:kristian.waagan@oracle.com]
> Sent: Thursday, 31 May 2012 1:45 AM
> To: builds@apache.org
> Subject: [Jenkins] poor handling of offline slaves
>=20
> Hi,
>=20
> Currently there are several jobs that have been hanging on a Linux =
executor
> for several days because windows1 is offline.

I've fixed the disk space issue by:

1. Clearing out some junk from Maven and/or poorly configured jobs that =
don=E2=80=99t
Clean up their workspaces.

2. I added a 80GB disk to replace the 40GB one.

>  In addition, there are a bunch
> of jobs that have been in the queue for days.

They will catch up.

> It appears that Jenkins lets the "multi OS" jobs wait for a very long =
time
> before giving up on waiting for a slave. A few questions:
>   a) Is it possible to have Jenkins fail a job already occupying an =
executor slot if
> it has to wait for too long?

If it is occupying an executor that means the build is running and/or =
stuck.
If stuck they can be configured to die after a while. With Windows =
builds this=20
Does not always work.

>   b) There's only one windows slave. Are there any plans to add =
another
> Windows slave (preferably on a different box than windows1)?

Not currently. When running well, there is never much of a queue demand =
for it.
Let it catch up and we'll review the situation again in a week.

>=20
> If many projects are configured to run on multiple operating systems, =
of
> which two have only one slave (Windows and Solaris), these projects =
may
> cause jobs to pile up on Linux. Maybe there are other mechanisms in =
place to
> deal with this, I don't know.

Not sure what you mean, jobs run independent of each other on multiple =
slaves.

>=20
> There are currently two other jobs [1]  that have been hanging for two =
days
> or more, but there seems to be enough Linux executors to serve other =
jobs
> reasonably fast. For that reason I have left them alone for the time =
being.

I'll delete those.

Gav...

>=20
>=20
> Thanks,
> --
> Kristian
>=20
> [1] https://builds.apache.org/job/Ant-Build-Matrix/ and
> https://builds.apache.org/job/Empire-db%20multios/