On Sat, Oct 22, 2011 at 11:19 PM, Stack wrote:
> Should we list machines we would build on Niklas? Currently we have 'ubuntu'
That should be just fine, this is a bug in Jenkins.
/niklas
Hi,
This has been sorted out now and our build is working fine again.
Lewis
On Sun, Oct 23, 2011 at 8:07 AM, lewis john mcgibbney <
lewis.mcgibb...@gmail.com> wrote:
> Hi,
>
> The clover option insists on failing our ant nightly builds. Even when I
> untick the clover option in the configuratio
The JMeter build failed on Solaris1 because the Ant installation there
is earlier than 1.8.0.
Does this need a JIRA to request an update, or is posting here sufficient?
Normally JMeter runs on ubuntu3.
However, recently I tried letting it run on any node.
That failed on Solaris1 (outdated Ant, see other posting), so I tried using
!solaris1
and was surprised to find that it ran on one of the hadoop nodes.
I would expect exclusions to apply to the default node s
On Sun, Oct 23, 2011 at 1:40 PM, sebb wrote:
> Normally JMeter runs on ubuntu3.
> However, recently I tried letting it run on any node.
>
> That failed on Solaris1 (outdated Ant, see other posting), so I tried using
>
> !solaris1
>
> and was surprised to find that it ran on one of the hadoop nodes
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: Sunday, 23 October 2011 9:37 PM
> To: builds@apache.org
> Subject: Jenkins Solaris1 has old Ant (pre 1.8.0)
>
> The JMeter build failed on Solaris1 because the Ant installation there is
> earlier than 1.8.0.
>
> Does th
On 2011-10-23 13:40, sebb wrote:
> Normally JMeter runs on ubuntu3.
> However, recently I tried letting it run on any node.
>
> That failed on Solaris1 (outdated Ant, see other posting), so I tried using
>
> !solaris1
>
> and was surprised to find that it ran on one of the hadoop nodes.
>
> I w
On Sun, Oct 23, 2011 at 3:41 PM, Dennis Lundberg wrote:
> This is the behavior that I expected. Using
>
> !solaris1
>
> would make the build run on any node except for the one called "solaris1".
Yes, but the hadoop slaves are configured to only allow for jobs bound
to those slaves. I don't think
This is a strange, strange bug - the polling log shows it polled on ubuntu5,
and even if master had executors and had the ubuntu label, that should still
mean the subsequent build would run on ubuntu5, since that's where the
previous build ran, and Jenkins will always opt to run where the previous
On Sun, Oct 23, 2011 at 7:32 PM, Andrew Bayer wrote:
> If someone can come up with a way to reliably reproduce this, I can dive in
> deeper.
That will probably be hard, given it has happen only twice in the ASF
installation as far as I know.
/niklas
10 matches
Mail list logo