Current backlog on Hudson doesn't seem to be Master, but the
Hudson-Slave1 and Hudson-Slave2 servers. The number of executors
on these machines is way to low for the number of jobs we have. I
noticed that the number of executors were greatly reduced yesterday.
Dave
On 09/30/2010 07:33 AM, Denis Roy wrote:
On 09/30/2010 10:25 AM, David M Williams wrote:
But, we can't all run all jobs on
master.
Well, why not. Since the master is virtualized, why don't we
goose it up and crank up the executor threads and see how it
goes? Maybe then we'll all be able to get some work done?
Is anyone game?
From: Matthias Sohn <matthias.sohn@xxxxxxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 09/30/2010 10:11 AM
Subject:
[cross-project-issues-dev]
cbi-papyrus-0.7-nightly
build is taking ages
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
This build seems to take ages, according to
Hudson it started Sep 30, 2010
3:11:46 AM
and now we have Sep 30, 2010 10:08:33 AM, anything wrong here or is this some massive
compile or test job ?
https://hudson.eclipse.org/hudson/job/cbi-papyrus-0.7-nightly/1105/console
I am just wondering since I am waiting since
hours for my few minutes egit build job
to grab a free worker thread.
--
Matthias_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
