Faré wrote:

Do you get any output?

We heavily modified run-tests.sh to be more robust with the way Windows implementations (fil to) parse command-line arguments; test-run-program has taken a beating, and the new test-stamp-propagation has never worked well on ABCL. Maybe we somehow broke something on ABCL?

In any case, on Linux x64, with the latest git checkout 27ee1d765b893c1765af7bf383fa7f9cb4b27590 I get no error with ABCL:

Using abcl Ran 48 tests: 48 passing and 0 failing all tests apparently successful

I *think* this is a make problem, not a problem with the abcl output. As you will see below, I get output and all the tests seem to pass successfully. But after the abcl tests pass, make does not complete and exit. Instead, it just hangs.

On Mon, Oct 21, 2013 at 5:44 PM, Robert P. Goldman rpgoldman@sift.net wrote:

...

Now when I run the tests with

make test-all-no-upgrade

I get to the end of the test process and I am left with:

-#--------------------------------------- Using abcl Ran 48 tests: 48 passing and 0 failing all tests apparently successful -#---------------------------------------

./test/run-tests.sh -c abcl

at this point, make hangs until I interrupt it with ^C.

Is it possible that I have messed up the way I conditionalized the test-bundle.script file?

What I did was add this:

#+(or abcl ecl) (leave-test "Bundle test doesn't work on Mac on this lisp." 0)

in my working copy. Could that be causing this hang?

thanks, r

On Mon, Oct 21, 2013 at 6:52 PM, Robert P. Goldman rpgoldman@sift.info wrote:

Looking at the make file, I see:

# test upgrade is a very long run... This does just the regression tests test-all-no-upgrade: @for lisp in ${lisps} ; do \ ${MAKE} test-lisp test-clean-load l=$$lisp || exit 1 ; \ done

I think that what's happening is that I'm actually getting a hang in test-clean-load on abcl. Testing test-clean-load separately on ABCL exhibits the hang:

$ make test-clean-load l=abcl ./test/run-tests.sh -c abcl

<nothing>

as does:

./run-tests.sh -c abcl

<nothing>

I don't really know what test-clean-load is supposed to do, so I can't comment further.

test-clean-load is supposed to prove that no warnings of any sort are emitted while loading ASDF as source code, that are not otherwise emitted by the implementation when not loading ASDF. Such messages are not just an aesthetic disgrace, but an actual nuisance in some situations (rarer now that implementations come with a proper ASDF if you just (require "asdf")).

Somehow, one of these tests may be failing to exit properly.

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Government's view of the economy could be summed up in a few short phrases : If it moves, tax it. If it keeps moving, regulate it. And if it stops moving, subsidize it. — Ronald Reagan (1986)