For me using the latest clisp on linux x64, all tests pass with 3.1.5.14. asdf-pathname-test.script fails with a segfault(!) at 3.1.5.15, due to commit 1b5bd7837874df7a89f697fa686eba6282e1f8e7 which changes comments and a default slot for class monolithic-lib-op, unused in that script. The segfault keeps happening until 3.1.5.17, and then pass again using 3.1.5.18, the only change being a tweak of docstrings(!). It keeps working until commit 540b7b9491280b3dae0c4b2b7160826edae559ca, but breaks again at commit d7a5bc7bdad09876efec3b678fa4e3bbc2dc995a which modifies unrelated function lisp-implementation-directory, now with an infinite loop or such while creating a system using logical-pathnames; but if I comment out the #+clisp line in that function, I'm back with the segfault, whereas if I put the entire expression in a #-clisp I get the test passing.
WTF, clisp? Using asdf commit a887b0c4c70c76efc750335d8178033aa5d58ac2, clisp changeset 15611:5c63938ef493.
The only way I see that mattering is via lisp-implementation-pathname-p, as called in parse-defsystem, at least for the latter failure. The segfault is clearly a CLISP bug.
I'll commit something that unbreaks it.
I cannot reproduce on my current machine with the latest clisp.
I'm too lazy to learn enough hg to checkout clisp at that specific changeset.