search

luismbo / cl-travis

Travis-CI scripts for testing Common Lisp software
MIT License
85 stars 18 forks source link

Software versions #27

Open zellerin opened 4 years ago

zellerin commented 4 years ago

While I understand that randomly changing software versions used is bad idea for regression testing, I would find useful to be able to test code against more recent lisp versions. Is that possible at the moment, or is there some reason why this is bad idea?

What I tried and failed:

I looked at the https://raw.githubusercontent.com/luismbo/cl-travis/master/install.sh and the download URLs are hardwired. I tried to factor out the version (i.e., SBCL_TARBALL_URL1="http://prdownloads.sourceforge.net/sbcl/sbcl-${SBCL_VERSION:-1.2.13}-x86-64-linux-binary.tar.bz2" ), and pass SBCL_VERSION=2.0.0 to sh +x but then my build end up with

+cim use sbcl-system --default
ln: failed to create symbolic link './sbcl': File exists
+compile_asdf
+echo Compiling ASDF...
Compiling ASDF...
+cl -c /home/travis/asdf.lisp -Q
/home/travis/.cim/bin/sbcl-system: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/travis/.cim/bin/sbcl-system)

so apparently it is not so easy.

luismbo commented 4 years ago

I think the latest version of SBCL might require a libc more recent than what Travis provides. This might be a good excuse to use Docker instead. This would help with testing locally, too. (Debugging test script via Travis is quite painful.) In any case, I agree with you that it'd be nice to have the option to upgrade Lisps more frequently.

Has anyone done a Docker image with Lisps and quicklisp pre-installed yet?