[racket-dev] Using Travis CI for Racket
I've just committed support for building Racket automatically on the Travis continuous integration service. See https://travis-ci.org/samth/racket/ for the current build state. This doesn't track the actual `plt/racket` repository yet [1], but once it does, it will do the following: - Build the core of Racket on every push (comparable to the "Minimal Racket" snapshot) - Run the tests relevant to that core. That's it -- this is a free service, and you can't take too much of their time. This isn't a replacement for DrDr, which runs _very_ comprehensive tests. But it provides very fast turnaround, multiple compilers, and eventually OS X and Windows builds. Initially, no one will get email -- let me know if you want to be emailed about build results. Currently, it runs tests for the following: - everything in `tests/racket/` - `json` - `xml` Unfortunately, that `pkg` tests seem to break right now. Let me know if there's something else that should be run to test that "Minimal Racket" is working. Sam [1] That should happen once Eli is back to flip the relevant configuration switch. _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Using Travis CI for Racket
This is cool. One way I've seen Travis CI help especially is with pull requests via GitHub. The integration is really nice. If someone's pull request breaks the build or tests, that is highlighted right there in the pull request "discussion thread" on GitHub. As a result, a contributor gets automatic feedback to fix it. BTW, I've wanted to use Travis CI for projects written _in_ Racket. What you did nudged me to try this, and I took some inspiration from https://github.com/RayRacine/rackos and came up with https://github.com/greghendershott/travis-racket. On Tue, Jul 2, 2013 at 7:04 PM, Sam Tobin-Hochstadt wrote: > I've just committed support for building Racket automatically on the > Travis continuous integration service. See > https://travis-ci.org/samth/racket/ for the current build state. This > doesn't track the actual `plt/racket` repository yet [1], but once it > does, it will do the following: > > - Build the core of Racket on every push (comparable to the "Minimal > Racket" snapshot) > - Run the tests relevant to that core. > > That's it -- this is a free service, and you can't take too much of > their time. This isn't a replacement for DrDr, which runs _very_ > comprehensive tests. But it provides very fast turnaround, multiple > compilers, and eventually OS X and Windows builds. Initially, no one > will get email -- let me know if you want to be emailed about build > results. > > Currently, it runs tests for the following: > > - everything in `tests/racket/` > - `json` > - `xml` > > Unfortunately, that `pkg` tests seem to break right now. > > Let me know if there's something else that should be run to test that > "Minimal Racket" is working. > > Sam > > [1] That should happen once Eli is back to flip the relevant > configuration switch. > _ > Racket Developers list: > http://lists.racket-lang.org/dev _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Using Travis CI for Racket
On Tue, Jul 2, 2013 at 7:04 PM, Sam Tobin-Hochstadt wrote: > I've just committed support for building Racket automatically on the > Travis continuous integration service. See > https://travis-ci.org/samth/racket/ for the current build state. This > doesn't track the actual `plt/racket` repository yet [1], This is now working -- thanks Eli. You can see the current status here: https://travis-ci.org/plt/racket If you'd like to be notified about tests, let me know. Unfortunately, some combination of the Travis configuration and recent changes to Racket mean that a few of the tests for `subprocess` are failing. Matthew thinks that the tests are the problem here, and I hope to look into this soon. > Currently, it runs tests for the following: > > - everything in `tests/racket/` > - `json` > - `xml` This list now includes `net`, `openssl`, `db`, `match` and the tests of embedded paths in zo files. Still not set up are: `pkg`, `launcher`, the relevant SRFIs, and a few other things. Sam _ Racket Developers list: http://lists.racket-lang.org/dev
