| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* tests/007/except-4.txr: The portable way to get a shell
command that exits with a signal is to execute kill -KILL $$.
If we use a signal that the shell catch like SIGTERM or
SIGINT, we get nonportable behaviors. Some shells seem to
catch the signal and then raise it again so they terminate
with that signal. Some shells terminate normally, but create
an exit status by OR-ing 0x80 with the caught signal.
Let's use kill -KILL here and drop the tests for BSD and
Solaris.
* tests/007/except-3.txr: Fix the kill command here also.
While this test wasn't failing on those platforms, it succeeds
vacuously, since the exception being ignored by :nothrow
is not actually thrown.
|
| |
|
|
|
|
|
|
| |
* tests/common.tl (os-symbol): Add :openbsd.
* tests/007/except-4.txr: Skip.
* tests/018/crypt.tl: Skip unsupported salts, i.e., without leading "$".
* tests/018/gzip.tl: Add -f to gzip command to force compression even if
it does not make the file smaller.
|
| |
|
|
|
|
|
| |
* tests/007/except-4.txr: This new test case does not work on
Solaris 10 because a shell script that kills itself via
kill $$ appears to be terminating successfully with an exit
status of 208, not appearing to be killed by a signal.
|
|
|
* tests/007/except-3.txr: New file.
* tests/007/except-3.expected: Likewise.
* tests/007/except-4.txr: Likewise.
* tests/007/except-4.expected: Likewise.
|
