Bug: return value of axecute() seems to be NULL instead of 0 or 1 according to this description

[Longfei2]

The return value of axecute() seems to be NULL instead of 0 or 1 according to this description.

[bms63]

Hi @Longfei2 thanks for the report. what is in your test.R file?

Wondering if the use of getwd() is causing issues.

[Longfei2]

There is the only codes of stop("aaaa") in test.R file. I don't know if the use of getwd() caused this issue? Or, I don't understand this description?

[bms63]

Could you try without getwd()

We actually realized that we don't have tests for this - so we might have something messed up on our end.

[Longfei2]

Dear,
There is the same value NULL.

[bms63]

It is an issue on our end and we will in next release! Thanks @Longfei2 !

[nicholas-masel]

I think our description mistakenly mixed up the return value of the function and the status returned from the overall execution.

If there is an error, we quit with a status of 1, but this only runs for non-interactive execution.