When you say "sbcl always passes" do you mean even when broken code is committed?
Where is the code for the travis builds kept? Do we have a repo containing the directives that travis follows? With regards to ditching travis if we can't figure out how to get the ccl/clisp builds to work properly, it seems that we're still better off with one of the platforms being tested, even if it means you have to investigate every failed travis build. It's not ideal, and it'd probably be worth it to either cut out or move the ccl/clisp builds to their own branch while we investigate what's wrong, but ditching travis all together is probably unnecessary. -E On 08/07/2015 03:34 AM, David Bjergaard wrote: > sbcl always passes, while clisp and ccl fail: > ccl: https://travis-ci.org/stumpwm/stumpwm/jobs/74369075 > clisp: https://travis-ci.org/stumpwm/stumpwm/jobs/74369077 > sbcl: https://travis-ci.org/stumpwm/stumpwm/jobs/74369074 > > David > > Evan <sire...@gmail.com> writes: > >> Can you give an example of how the travis builds are broken? >> >> -E >> >> On 08/06/2015 03:16 AM, David Bjergaard wrote: >>> Hi, >>> >>> Does anyone know how to fix the travis builds? Its making it really hard to >>> know >>> if its safe to merge PRs or if I'm not breaking stuff. If it can't be >>> fixed, I >>> would prefer that we remove it and go back to the old way (waiting for bug >>> reports :$) >>> >>> Dave >>> >>> _______________________________________________ >>> Stumpwm-devel mailing list >>> Stumpwm-devel@nongnu.org >>> https://lists.nongnu.org/mailman/listinfo/stumpwm-devel >>> _______________________________________________ Stumpwm-devel mailing list Stumpwm-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/stumpwm-devel
