FWIW, the ideal solution would be if it did what Travis does and tested against pull requests and commented there for any failures. Almost no one looks at the Travis logs against master; people look at them against pull requests. But if this is not technically possible, or if it would require more build power than you are willing to donate, then we will need to find another solution.
A reasonable workaround might be to comment on the pull request that (apparently) broke master. Since the HEAD of master is almost always a GitHub pull request merge commit, this should work. The disadvantage of course is that you're telling someone that their pull request broke something *after* it was merged. Aaron Meurer On Sun, Aug 18, 2013 at 11:52 PM, Matthew Brett <[email protected]> wrote: > Hi, > > On Sun, Aug 18, 2013 at 3:52 PM, Aaron Meurer <[email protected]> wrote: >> On Sun, Aug 18, 2013 at 12:11 AM, Matthew Brett <[email protected]> >> wrote: >>> Hi, >>> >>> On Sat, Aug 17, 2013 at 3:02 PM, Matthew Brett <[email protected]> >>> wrote: >>>> Hi, >>>> >>>> On Fri, Aug 16, 2013 at 10:15 AM, Jason Moore <[email protected]> wrote: >>>>> Sounds good to me. I can work on it but am not familiar with buildbot. Any >>>>> quick tips to get me started? Or if it is simple for you to add then, I'll >>>>> watch what you add to learn. >>>> >>>> Here's a first pass: >>>> >>>> http://nipy.bic.berkeley.edu/builders/sympy-py2.7-32/builds/1/steps/shell_3/logs/stdio >>>> >>>> https://github.com/nipy/nibotmi/commit/e1020352c009ef3ed3178edc3aa4f8093dc57d06 >>> >>> Now passing after some tweaks: >>> >>> http://nipy.bic.berkeley.edu/builders/sympy-py2.7-32/builds/8/steps/shell_3/logs/stdio >>> >>> Your own private waterfall of (one lonely) sympy builder: >>> >>> http://nipy.bic.berkeley.edu/waterfall?category=sympy >>> >>> Adding more build configurations is now pretty trivial. >>> >>> If you don't want to run on our system then it would be fairly easy to >>> set up an Amazon instance with a version of our setup, and I'm sure >>> you could find volunteers to act as buildslaves: >>> >>> https://github.com/nipy/nibotmi/blob/master/install.rst >>> >>> Currently it's only me who gets an email when the sympy build breaks, >>> let me know what you'd like to do about notifications. >> >> I still haven't thought of anything. I guess at least for now add my >> email to the notification list. > > Two obvious suggestions would be a sympy-testing mailing list, and / > or enabling email to the committer for the broken commit. > > Cheers, > > Matthew > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sympy. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. For more options, visit https://groups.google.com/groups/opt_out.
