buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Grotzke <martin.grot...@javakaffee.de>
Subject Re: Issues running with USE_FSC: Could not connect to compilation daemon
Date Fri, 14 Aug 2009 17:30:00 GMT
On Fri, 2009-08-14 at 08:00 -0400, Daniel Spiewak wrote:
> I'm not even sure this is possible.  Buildr simply delegates to the fsc
> command, so we only have as much control as that command exposes (virtually
> none).  I would be willing to make the timeout configurable at the Buildr
> level if indeed it is possible to configure it in the arguments sent to fsc.
> 
> As for the underlying problem...  That's one I haven't seen except on Mac,
> when it is usually due to firewall issues.  Is it possible that you're
> running more than one build simultaneously?  I suspect that fsc doesn't
> handle that case particularly well.
Our CI server hudson definitely runs different jobs in parallel. Though,
there's no other project here using scala (and fsc), and hudson
shouldn't build our project in parallel. So I'd suspect that it's just
the load that causes the timeout.

Thanx && cheers,
Martin


> 
> Daniel
> 
> On Fri, Aug 14, 2009 at 7:13 AM, Martin Grotzke <
> martin.grotzke@javakaffee.de> wrote:
> 
> > Hi,
> >
> > on our CI server our build often fails with the message
> >  "Could not connect to compilation daemon"
> >
> > The CI server has lots of jobs to execute, and we suppose that the
> > relatively high load is causing this issue.
> >
> > Now I wonder if this is an issue of fsc itself, or if the buildr
> > compiler plugin for scala/fsc could increase the timeout to wait for
> > fsc.
> >
> > What do you think?
> >
> > Cheers,
> > Martin
> >
> >

Mime
View raw message