[asdf-devel] New failures on Allegro Windows

[Faré]

On Mon, Oct 14, 2013 at 10:02 PM, Dave Cooper <david.cooper at genworks.com> wrote:
>
> With latest pull (with 3.0.2.22) I'm getting one failure on mlisp windows
> and two on alisp windows (a few pulls ago, alisp windows was passing all
> tests and mlisp was unknown but apparently failing several which are
> apparently all fixed now, because the one mlisp failure does not appear
> casemode related):
>
The run-program failure I understand: because on allegro, I decided to NOT
tuck in an additional cmd /c, so some program echo.exe gets executed, and
the space is eaten by the regular argument parsing. We'd have to explicitly
"cmd /c echo ok  1" on allegro.

I moved that test to the unix-only section. Something more clever will
have to be written
to test the functionality on Windows.

I'm surprised that the test-stamp-propagation would run on mlisp but not alisp.
I increased sleep 1 to sleep 2, hoping that will make the test more
deterministic.

Can you pull and try again?

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
Maybe Jesus was right when he said that the meek shall inherit the earth
— but they inherit very small plots, about six feet by three.
        — Robert Heinlein, "Time Enough For Love"