git.fiddlerwoaroof.com
.travis.yml
8e0817b0
 language: lisp
 sudo: required
 
 env:
   matrix:
     - LISP=sbcl
     - LISP=ccl
07de0bcb
     - LISP=abcl
     - LISP=allegro
8e0817b0
     - LISP=clisp
     - LISP=cmucl
     - LISP=ecl
 
 matrix:
   allow_failures:
     # CIM not available for CMUCL
     - env: LISP=cmucl
     # issue #16
     - env: LISP=allegro
16aec0ae
     - env: LISP=clisp
     - env: LISP=abcl
     - env: LISP=ecl
8e0817b0
 
 # either use a local install.sh script or install it via curl. Feel
 # free to simplify this section in your own .travis.yml file.
 install:
   - if [ -x ./install.sh ] && head -2 ./install.sh | grep '^# cl-travis' > /dev/null;
     then
       ./install.sh;
     else
       curl https://raw.githubusercontent.com/luismbo/cl-travis/master/install.sh | sh;
     fi     
5333bbea
   - 'pushd $HOME/quicklisp/local-projects &&
      git clone http://git.elangley.org/git/u/edwlan/fwoar.lisputils.git &&
      git clone http://git.elangley.org/git/u/edwlan/vector-update-stream.git;
      popd'
8e0817b0
 
 # this serves as an example of how to use the 'cl' script (provided by
 # CIM) to test your Lisp project. Here, we're using the RT framework
 # to do unit testing; other frameworks will have different ways of
 # determining whether a test suite fails or succeeds.
 script:
ba3e376e
   - pwd && ls && cl -e '(push (truename ".") asdf:*central-registry*)'
62dfc4c4
        -e '(ql:quickload :stream-provider)'
ba3e376e
   - pwd && ls && cl -e '(push (truename ".") asdf:*central-registry*)'
ce1e953b
        -e '(ql:quickload :stream-provider.test)'
        -e '(asdf:test-system :stream-provider)'
8e0817b0
     [ $? -eq 1 ]