Comment 1 for bug 1490587

I believe this is an ECL bug, which I have reported upstream:
https://gitlab.com/embeddable-common-lisp/ecl/issues/149

Indeed, if I add a #+ecl t in the force-shell test of the final run-program function, it all works for me, whereas if I don't, the new (to ecl) use-run-program backend fails erratically with an error that suggests I got NIL as an exit code where 0 was expected.