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.clktrk _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
