Closed saikyun closed 2 years ago
I was able to reproduce this in a Windows environment using jpm at the latest commit and janet at the latest commit.
On a side note, behavior was as expected under a Linux environment -- i.e.
$ jpm test
running test/error.janet ...
error: wat
in _thunk [test/error.janet] (tailcall) on line 1, column 1
non-zero exit code in test/error.janet: 1
running test/exit.janet ...
non-zero exit code in test/exit.janet: 1
Failing test scripts: 2
Looks like this was an error in Janet, has been fixed on master: https://github.com/janet-lang/janet/commit/427f7c362e19117c6ac91b9fe2419019c0adbeb3
We were using the wrong member of a structure to get the return value of the process.
I still get similar errors. May be I didn't update appropriately.
Perhaps @saikyun wouldn't mind trying?
I can confirm the update works - tested with latest master and spork with a fake bug introduced.
Confirmed it's working here. I think I misinterpreted the output before. Sorry about that.
Using either:
jpm test
seems to always return 0.Example:
The tests are running
(error "wat")
and(os/exit 1)
.