On May 4, 2012, at 7:33 PM, Steve Ebersole wrote:
> Touche ;)
>
> Ok I'll just chaulk it up to that then.
>
> Overall do you think that is an issue with Jenkins? Or with the JBoss setup?
>
>
not sure, but we may improve this.
the slaves used by Jenkins can be labeled, and all hibernate jobs
Touche ;)
Ok I'll just chaulk it up to that then.
Overall do you think that is an issue with Jenkins? Or with the JBoss setup?
On May 3, 2012 11:15 PM, "Strong Liu" wrote:
>
> On May 4, 2012, at 3:45 AM, Steve Ebersole wrote:
>
> But I killed it and #243 started *immediately*
>
>
> well, you al
On May 4, 2012, at 3:45 AM, Steve Ebersole wrote:
> But I killed it and #243 started *immediately*
well, you already know, it sucks
>
> On Thu 03 May 2012 02:39:13 PM CDT, Strong Liu wrote:
>> I think it was just waiting for next available executors, basically
>> there were too many jobs in qu
But I killed it and #243 started *immediately*
On Thu 03 May 2012 02:39:13 PM CDT, Strong Liu wrote:
> I think it was just waiting for next available executors, basically
> there were too many jobs in queue waiting to be run
>
> On May 4, 2012, at 3:27 AM, Steve Ebersole wrote:
>
>> Strong, I had
I think it was just waiting for next available executors, basically there were
too many jobs in queue waiting to be run
On May 4, 2012, at 3:27 AM, Steve Ebersole wrote:
> Strong, I had to kill hibernate-core-master-matrix job #242. It had
> been hanging for the last 8+ hours without every eve