Running test-run-program.script with ecl-16.0.0-unknown-macosx-x64
Testing echo ok 1 via run-program as a list
Testing echo ok 1 via run-program as a string
Testing true via run-shell-command
Testing false via run-shell-command
Testing bad shell command via run-shell-command
Testing good shell command in current directory via run-shell-command
Testing awkward legacy output capture via run-shell-command
Can we echo a simple string?
Are spaces handled properly?
Test that run-program fails properly with an empty program string
An empty string itself is ok since it is passed to the shell.
Test that run-program fails properly with a nil program list
Test that run-program fails properly when the executable doesn't exist.
Checking whether (RUN-PROGRAM '("does-not-exist") :OUTPUT :LINES) signals ERROR
Received signal #<a UIOP/RUN-PROGRAM:SUBPROCESS-ERROR>
Checking whether (RUN-PROGRAM "does-not-exist" :OUTPUT :LINES) signals ERROR
Received signal #<a UIOP/RUN-PROGRAM:SUBPROCESS-ERROR>
Checking that spaces between arguments are collapsed by shell when and only when unquoted
Checking behavior on program success or failure
Checking whether (RUN-PROGRAM "false") signals SUBPROCESS-ERROR
Received signal #<a UIOP/RUN-PROGRAM:SUBPROCESS-ERROR>
Tests with test-file
TEST ABORTED: Subprocess (:OUTPUT-STREAM
#<closed two-way stream 0000000109d48960> :PROCESS
#S(EXT:EXTERNAL-PROCESS :EXT::PID NIL :EXT::INPUT #<two-way stream 000000010834bdc0> :EXT::OUTPUT #<input stream "grep"> :EXT::ERROR-STREAM #<two-way stream 000000010834bdc0> :EXT::%STATUS :EXITED :EXT::%CODE 0))
with command ("grep" "[\\]" "/Users/rpg/lisp/asdf/test/test-file")
exited with error
I believe this is an ECL bug, which I have reported upstream:
https:/