On 02/20/2011 05:42 PM, Jason Edgecombe wrote:
Hi everyone,
At Andrew Deason's suggestion, I have added a "cat config.log" buildstep
to the debian-i386, debian-arm, and fedora-arm builders. These builders
share the same buildfactory. I'm a little concerned that the config.log
file is ~852K and that is uploaded with each build.
Any opinions on whether or not to include this? I hesitate because of
the bandwidth involved, and I know one of the buildslaves had issues
with saturating it's upstream pipe.
Jason
I've been thinking about this, especially after seeing something like
400kbps worth of uncompressed compiler text output (MIPSPro C is quite
verbose) flowing over the wire. While digging around the online docs to
see if there was any compression options for slave output, I noticed
that Buildbot has the capability to send files from the slave to the
master. If we were to gzip, for instance, config.log and upload the
compressed output, would that work for your needs, Andrew?
Alternatively, we could look at using something like stunnel with
compression to send the compiler output back to the master.
____________________________________________________________
Send any screenshot to your friends in seconds...
Works in all emails, instant messengers, blogs, forums and social networks.
TRY IM TOOLPACK at http://www.imtoolpack.com/default.aspx?rc=if2 for FREE
_______________________________________________
OpenAFS-devel mailing list
OpenAFS-devel@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-devel
