From: Reini U. <rei...@gm...> - 2018-02-02 00:44:36
|
On Thu, Feb 1, 2018 at 8:58 PM, Bruno Haible <br...@cl...> wrote: > Hi Reini, > > > There’s the ci branch with the travis and appveyor smokes. > > You mean, the files .travis.yml and .appveyor.yml in > https://github.com/rurban/clisp ? > The ci branch contains those two files, plus the patches and recipes for smokes on those 3 platforms. I forgot if sigsegv works on win64 already, I did the utils/libsigsegv-win64.patch 2017. ffcall needs utils/libffcall-1.13-20170225-funbegin.patch > > > For the first time since I started smoking clisp, all the linux and OS X > tests passed by today. > > Do you mean, your work on .travis.yml and .appveyor.yml is completed? > No. Those branches were completed March 2017. It could also be used to produce binary releases, as described in those files. > > Or do you mean, the many bug fixes in the clisp repository, from the last > year, > are showing positive effects even on the "mainstream" platforms? > Exactly. It still doesn't work on my debian-testing, but on a stock ubuntu as from travis it started now working. > > Or do you mean, avoidable test suite failures are now properly avoided by > conditionalization? > > (Sorry for the questions; I couldn't parse the intent of your message.) > > No, most of the test problems still need my patches, from the bugfixes branch. But at least core clisp passes its own testsuite on the major platforms. I.e. the homegrown GC and module problems from last year. threads and jit have still a lot todo, and the translation is only about 70% done. -- Reini Urban |