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
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 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
Should we list machines we would build on Niklas? Currently we have 'ubuntu'
St.Ack
On Sat, Oct 22, 2011 at 4:57 AM, Niklas Gustavsson wrote:
> On Sat, Oct 22, 2011 at 5:31 AM, Ted Yu wrote:
>> Please see the hanging build:
>> https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.92/78/cons
On Sat, Oct 22, 2011 at 5:31 AM, Ted Yu wrote:
> Please see the hanging build:
> https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.92/78/console
>
> It would be nice to know where the build got hung.
For whatever reason, Jenkins decided to run this build on master. But,
we don't allow bui
Hi,
Please see the hanging build:
https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.92/78/console
It would be nice to know where the build got hung.
Thanks