No -- I hit the limits, too. :( One of my challenges in getting patches in is that I have no reliable way of validating. Validating locally is possible, but it gets false negatives (Mac validation usually isn't clean) and is inconvenient. I will be working with my school's sysadmin to get a Linux server working to do this, but not everyone has that possibility.
Richard > On Sep 3, 2017, at 9:55 AM, Joachim Breitner <[email protected]> wrote: > > Hi Richard, > > I saw you tried to get Travis working again. I also gave it a quick > shot (in wip/travis2), but hit time limits again. Did you have more > luck? > > Greetings, > Joachim > > Am Montag, den 21.08.2017, 23:17 -0400 schrieb Richard Eisenberg: >> I have not been getting emails from Travis, despite using it for >> other projects (and thus being registered). So perhaps something is >> going wrong there. Regardless, it's useful for me, even without the >> emails. >> >> Another nice thing about Travis: I can get a quick check of the >> history of failures, even in DEBUG mode. >> >> Richard >> >>> On Aug 21, 2017, at 3:54 AM, Joachim Breitner <mail@joachim-breitne >>> r.de> wrote: >>> >>> Hi, >>> >>> Am Sonntag, den 20.08.2017, 23:55 -0400 schrieb Richard Eisenberg: >>>> The big minus to Travis, as I see it, are that only committers >>>> can >>>> use it. (A forked repo just doesn't work because of the way that >>>> submodules are checked out, IIRC.) This minus doesn't affect me, >>>> however. >>> >>> I think the biggest minus is that Travis can either be configured >>> to >>> send mails to one specific address (as it was initially, when I >>> received all the mail and could check whether I want to notify the >>> author), or to the author of the patch, but not both. Currently it >>> is >>> sent to notify the author, but people seem to simply ignore the >>> mails. >>> >>> (Or maybe even only authors who also registered on travis get >>> them?) >>> >>> So if there is demand to keep using Travis, maybe we have to go >>> back to >>> sending notification mails to one person who oversees this service? >>> >>> Joachim >>> >>> >>> >>> -- >>> Joachim Breitner >>> [email protected] >>> http://www.joachim-breitner.de/ >>> _______________________________________________ >>> ghc-devs mailing list >>> [email protected] >>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs >> >> _______________________________________________ >> ghc-devs mailing list >> [email protected] >> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > -- > Joachim “nomeata” Breitner > [email protected] > https://www.joachim-breitner.de/ > _______________________________________________ > ghc-devs mailing list > [email protected] > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs _______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
