[Scilab-users] test_run failed: Slave Scilab exited with error code 127

[Samuel Gougeon]

Le 02/08/2019 à 10:08, philippe a écrit :
> Le 01/08/2019 à 22:29, Samuel Gougeon a écrit :
>>
>> Sorry for you. I can't reproduce on Win7.
>> You may search to which issue the exit code 127 (coming from the 
>> shell of your OS) corresponds.
>
> on linux error code 127 should stand for  "command not found"
>
>>
>> In addition,  do the tests pass when you exec() them (for instance 
>> from Scinotes) ?
>
> yes I can execute *.tst files without errors


In test_run.sci
edit test_run
you may insert
disp(test_cmd)
in absolute line 891, just before launching the slave session with

returnStatus  =  host(test_cmd);

And see what it is.
Or use debug() in the same purpose: know what is actually sent to the shell.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/users/attachments/20190802/9239e9a7/attachment.htm>