On Thu, Oct 04, 2007 at 02:09:01PM -0400, David Golden wrote: > Slaven Rezic has figured out that some test reports are exceeding the > 400K maximum size that develooper.com will accept. It seems > reasonable to truncate the test output included. (Maybe long term > gzip and attach instead.)
I've noticed it too, but not bothered mentioning it because I thought everyone knew :-) > 400K seems like a lot. Ask has suggested it be smaller, but hasn't > specified a size. > > What do you all think would be a reasonable maximum? 100K? 200K? >From a quick look over the reports I've sent this month, 40K looks like a good cutoff point. Add the introductory text, perl -V, and any comments I might add by hand, and it'll still be well under 50K. Can I also suggest - probably for the future as it would require more work - some way of automatically killing off a test that has done nothing but spew megabyte after megabyte after megabyte of errors and warnings to the console, and just make it a FAIL? Spewing a gazillion warnings is generally considered to be a Bad Thing even if they're harmless and the code actually works. -- David Cantrell | http://www.cantrell.org.uk/david Irregular English: you have anecdotes; they have data; I have proof
