Re: [cross-project-issues-dev] 2 executors instead of 4 question ...

[Laurent Goubet <laurent.goubet@xxxxxxx>]

Hi David,

Thanks for the response, at least I know what triggerred the change :). 
I think it would be interesting to go all the way and "split slave1 into 
2-3 slaves" yes; there are many jobs running on slave1, and 2 executors 
don't seem to do the trick more often than not (release days, morning 
"CET" when all "nightlies" begin to run, effectively preventing us to 
build anything until the queue is entirely built...).

I mentionned it as an aside, but this is aggravated by the fact we 
cannot build on master and are thus tied down to slave1. I'll need to 
try again now, but I am pretty sure I'll stumble once again on the bug 
Adolfo and I hit for our builds earlier this year (something with hudson 
unable to find jdt.junit4 ... see this old cross-project thread for 
reference : 
http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg06420.html).

Laurent Goubet
Obeo

On 18/01/2012 19:42, David M Williams wrote:
> > As a side note, I may have missed the notification but ... why has
> > slave1 been limited to 2 executors instead of the previous 4? It gets
> > extremely hard to get a build to run on that hudson instance now with
> > all the builds tied to it (the virgo nightlies come to mind as they
> > often take all executors on the morning -CET-).
> I never did see this answered ... so, will say what I know ... see bug
> 366672 [1]. In short, rumor has it Hudson is "more stable" with 2 rather
> than with 4.
>
> But, I agree something seems amiss ... it seems every time I've looked at
> Hudson this week there have been many builds "backed up".  If we have less
> executors, do we need more slaves? (Geez ... who comes up with these
> words ... 'executors' ... 'slaves' :)
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=366672#c12
>
>
>
>
> From:	Laurent Goubet<laurent.goubet@xxxxxxx>
> To:	"cross-project-issues-dev@xxxxxxxxxxx"
>              <cross-project-issues-dev@xxxxxxxxxxx>,
> Date:	01/17/2012 10:39 AM
> Subject:	[cross-project-issues-dev] EMF Compare 1.2.2RC1 will be late
> Sent by:	cross-project-issues-dev-bounces@xxxxxxxxxxx
>
>
>
> Hi all,
>
> The EMF Compare SR2 RC1 build (1.2.2 RC1) will be late. We have some
> dependencies issue and have a hard time running builds to test. We are
> tied to hudson-slave1 because of cryptic errors on master... and that
> instance is irresponsive.
>
> As a side note, I may have missed the notification but ... why has
> slave1 been limited to 2 executors instead of the previous 4? It gets
> extremely hard to get a build to run on that hudson instance now with
> all the builds tied to it (the virgo nightlies come to mind as they
> often take all executors on the morning -CET-).
>
> Best regards,
>
> Laurent Goubet
> Obeo
> [attachment "laurent_goubet.vcf" deleted by David M Williams/Raleigh/IBM]
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

begin:vcard
fn:Laurent Goubet
n:Goubet;Laurent
org:<a href="http://www.obeo.fr";>Obeo</a>
email;internet:laurent.goubet@xxxxxxx
url:http://www.obeo.fr
version:2.1
end:vcard