I'm a fan of anything automated that can prevent mistakes. Running `lookForTabs` with traivs could be handy as well.
-Kyle On 9/8/14, 3:08 PM, "Thomas Van Doren" <[email protected]> wrote: >I like the ideas of using travis! I actually started a branch long ago to >add a .travis.yml to the repo, which I just updated: > >https://github.com/chapel-lang/chapel/pull/342 > > >Back then it was taking 60+ minutes to run the builds, but I think it >would be fast enough now with the smoke test script. I also like that the >status is integrated into the pull request UI, making it easy for >reviewers and devs to find out if/when something is broken. > >What do others think? > >Here is more information about how travis integrates with github pull >requests: > >http://blog.travis-ci.com/2012-09-04-pull-requests-just-got-even-more-awes >o >me/ > > > >On 9/8/14, 2:48 PM, "Francisco Souza" <[email protected]> wrote: > >>Hello hello, >>Earlier today I broke your smoke tests with pull request #325 :( Sorry >>about that. >> >>I figured out we could use travis for running smoke tests on every >>pull request, so contributors can see the impact of their changes in >>the tests. >> >>This can be expanded to other tasks as well, like ``make test``. >> >>A good thing about travis, is that it can generate a build matrix >>based on environment and compilers, and it already supports gcc and >>clang. Here's a still broken example, from my fork: >>https://travis-ci.org/fsouza/chapel/builds/34755579 >> >>Any thoughts on this? >> >>Regards, >>Francisco >> >>------------------------------------------------------------------------- >>- >>---- >>Want excitement? >>Manually upgrade your production database. >>When you want reliability, choose Perforce >>Perforce version control. Predictably reliable. >>http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clk >>t >>rk >>_______________________________________________ >>Chapel-developers mailing list >>[email protected] >>https://lists.sourceforge.net/lists/listinfo/chapel-developers > > >-------------------------------------------------------------------------- >---- >Want excitement? >Manually upgrade your production database. >When you want reliability, choose Perforce >Perforce version control. Predictably reliable. >http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clkt >rk >_______________________________________________ >Chapel-developers mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/chapel-developers ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
