[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: build cluster for all architectures.

On Thu, 27 May 1999, Ben Collins wrote:

> On Thu, May 27, 1999 at 01:31:13PM -0400, shaleh@clifford.livenet.net wrote:
> > > 
> > > 
> > > Ben,
> > > 
> > > what you propose here, sounds very reasonable to me. 
> > > 
> > > One criticism: 
> > > 
> > > For most dialup developers, it will be very inconvinient to work on
> > > this cluster.  So writing the fail logs in the home directory will be
> > > of little use.
> > > 
> > 
> > So how about a submit queue.  You submit the source for compiling, and it mails
> > you the results.  If it fails you do another submit.
> Mailing would have to be an option (perhaps mail to the local account
> the the build system and allow .forward for sending to alternative
> emails). From experience, these build logs can by between 50 to 2000k
> and more. Also from experience though, most of the useful fail
> information is in the last 100 lines or less (food for thought).

Well, then: mailing the tail --lines=200 to the maintainer. I guess this
will be easy to implement (I haven't worked on the build daemon, so
what do the experts say?). 

Maybe the mail could indicate the true length of the build log and if you
reply to the mail, the log is send to you completely (compressed, split
and mime or uuencoded --- but that would be real work to do. I would do
that by generating a cookie which will be part of the subject line (A
simple consecutive number). The Reply-To is set appropiately and the mail
is piped by .procmailrc to a perl script. The script matches the
cookie against a simple database, so it knows which log to send.)

I really would like to have this feedback. 


P.S.: Please vote against Spam! At
(Sorry Europeans only)
Jens.Ritter@weh.rwth-aachen.de   grimaldi@debian.org
Key ID: 2048/E451C639 Jens Ritter
Key fingerprint: 5F 3D 43 1E 24 1E CC 48  1E 05 93 3A A7 10 73 37 

Reply to: