On 9/23/07, Joseph Heck <[EMAIL PROTECTED]> wrote: > > I'm also a little concerned that the noise level would be high for > those messages - that ultimately people would ignore them because of > frequency.
The current state of the tree is a little misleading; Post-sprint, we have had a few test failures, but most of the time, the test suite should be in a passing state. > Maybe a separate list just for the buildbot output? I'm open to suggestions... Sounds like a good idea to me. A 'build errors only' list would be relatively low traffic, and could be easily ignored at individual discression. Another approach would be to only send the failure message to the committer that stimulated the build. i.e., you break it, you get a nastygram in your inbox :-) On a related note - - Have we got any documentation pointing to the existence of the buildbot? I was thinking that it should be mentioned somewhere on the 'how to contribute' page. - The build last night ([6407]) should have passed, but the Postgres build seems to have crapped out due to taking too long. Is the test max duration a setting that is being too conservative here, or has something else gone wrong? Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
