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

classic Classic list List threaded Threaded
15 messages Options
Philippe Roux Philippe Roux
Reply | Threaded
Open this post in threaded view
|

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

Hi,

I've just move to a new laptop and I try to rebuild toolboxes I've
created for scilab-6.0.2, every thing looks fine except that all unit
tests fail ! I realize that in fact ALL SCILAB unit tests fail  with the
same error message :


--> test_run([],[],'no_check_ref')
    TMPDIR = /tmp/SCI_TMP_7851_f13kzL

  Module  001/074 - [action_binding] :


  Module  002/074 - [api_scilab] :

    001/053 - [api_scilab] booleanExample........................failed:
Slave Scilab exited with error code 127
    002/053 - [api_scilab] booleanSparseExample..................failed:
Slave Scilab exited with error code 127
    003/053 - [api_scilab] boolean_writing_api...................failed:
Slave Scilab exited with error code 127
    004/053 - [api_scilab] calloverloadfunction_api..............failed:
Slave Scilab exited with error code 127
    005/053 - [api_scilab] check_matrix_dimension................failed:
Slave Scilab exited with error code 127
    006/053 - [api_scilab] common_function.......................failed:
Slave Scilab exited with error code 127
    007/053 - [api_scilab] common_list_api.......................failed:
Slave Scilab exited with error code 127


Can someone tell me What is wrong here ?

Philippe

_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users
Samuel GOUGEON Samuel GOUGEON
Reply | Threaded
Open this post in threaded view
|

Re: test_run failed: Slave Scilab exited with error code 127

Le 01/08/2019 à 14:22, philippe a écrit :

> Hi,
>
> I've just move to a new laptop and I try to rebuild toolboxes I've
> created for scilab-6.0.2, every thing looks fine except that all unit
> tests fail ! I realize that in fact ALL SCILAB unit tests fail  with
> the same error message :
>
>
> --> test_run([],[],'no_check_ref')
>    TMPDIR = /tmp/SCI_TMP_7851_f13kzL
>
>  Module  001/074 - [action_binding] :
>
>
>  Module  002/074 - [api_scilab] :
>
>    001/053 - [api_scilab]
> booleanExample........................failed: Slave Scilab exited with
> error code 127
>    002/053 - [api_scilab]
> booleanSparseExample..................failed: Slave Scilab exited with
> error code 127
>    003/053 - [api_scilab]
> boolean_writing_api...................failed: Slave Scilab exited with
> error code 127
>    004/053 - [api_scilab]
> calloverloadfunction_api..............failed: Slave Scilab exited with
> error code 127
>    005/053 - [api_scilab]
> check_matrix_dimension................failed: Slave Scilab exited with
> error code 127
>    006/053 - [api_scilab]
> common_function.......................failed: Slave Scilab exited with
> error code 127
>    007/053 - [api_scilab]
> common_list_api.......................failed: Slave Scilab exited with
> error code 127


Yes, it's a bad start, but it's just for the api_scilab module
(unfortunately it's the first tested one :/)
Just try with the next one:
test_run("ast",[],"no_check_ref")

It's OK.

Samuel


_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users
Philippe Roux Philippe Roux
Reply | Threaded
Open this post in threaded view
|

Re: test_run failed: Slave Scilab exited with error code 127

Le 01/08/2019 à 18:19, Samuel Gougeon a écrit :
>
> Yes, it's a bad start, but it's just for the api_scilab module
> (unfortunately it's the first tested one :/)
> Just try with the next one:
> test_run("ast",[],"no_check_ref")


no all tests fail (excepts those who are skipped automatically) :


--> test_run("ast",[],"no_check_ref")
    TMPDIR = /tmp/SCI_TMP_20383_fZszyE

  Module  001/001 - [ast] :

    001/154 - [ast] Sand.........................................failed:
Slave Scilab exited with error code 127
    002/154 - [ast] Sor..........................................failed:
Slave Scilab exited with error code 127
    003/154 - [ast] addition.....................................failed:
Slave Scilab exited with error code 127
    004/154 - [ast] addition_output_type.........................failed:
Slave Scilab exited with error code 127
    005/154 - [ast] analysis1....................................failed:
Slave Scilab exited with error code 127
    006/154 - [ast]
analysis2....................................skipped: not yet fixed

....


 
--------------------------------------------------------------------------
    Summary

    tests            150 - 100 %
    passed             0 -   0 %
    failed           150 - 100 %
    skipped            4
    length             6.18 sec
 
--------------------------------------------------------------------------
    Details



    TEST : [ast] Sand
    failed: Slave Scilab exited with error code 127


    TEST : [ast] Sor
    failed: Slave Scilab exited with error code 127


    TEST : [ast] addition
    failed: Slave Scilab exited with error code 127


    TEST : [ast] addition_output_type
    failed: Slave Scilab exited with error code 127


    TEST : [ast] analysis1
    failed: Slave Scilab exited with error code 127




fresh install of scilab-6.0.2  on ubuntu 18.04 :


Version de Scilab : 6.0.1.1550134035 <=supposed to be scilab-6.0.2!
Système d'exploitation : Linux 4.15.0-1045-oem
Version Java : 1.8.0_151
Informations sur l'environnement d'exécution Java : Java(TM) SE Runtime
Environment (build 1.8.0_151-b12)
Informations sur la machine virtuelle Java : Java HotSpot(TM) 64-Bit
Server VM (build 25.151-b12, mixed mode)
Spécifications du fabricant : Oracle Corporation

but fortunately uman looks to work now ;-)

Best regards
Philippe

_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users
Samuel GOUGEON Samuel GOUGEON
Reply | Threaded
Open this post in threaded view
|

Re: test_run failed: Slave Scilab exited with error code 127

Le 01/08/2019 à 22:16, philippe a écrit :

> Le 01/08/2019 à 18:19, Samuel Gougeon a écrit :
>>
>> Yes, it's a bad start, but it's just for the api_scilab module
>> (unfortunately it's the first tested one :/)
>> Just try with the next one:
>> test_run("ast",[],"no_check_ref")
>
>
> no all tests fail (excepts those who are skipped automatically) :
>

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.

In addition,  do the tests pass when you exec() them (for instance from
Scinotes) ?


_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users
Samuel GOUGEON Samuel GOUGEON
Reply | Threaded
Open this post in threaded view
|

Re: test_run failed: Slave Scilab exited with error code 127

In reply to this post by Philippe Roux
Le 01/08/2019 à 22:16, philippe a écrit :
> Le 01/08/2019 à 18:19, Samuel Gougeon a écrit :
>>
>> Yes, it's a bad start, but it's just for the api_scilab module
>> (unfortunately it's the first tested one :/)
>> Just try with the next one:
>> test_run("ast",[],"no_check_ref")
>
>
> no all tests fail (excepts those who are skipped automatically) :


This could come from an autoloaded ATOMS module, if any.
You may try canceling the autoloading of all your installed modules, and
then rerun test_run.

[a new test_run() option running all slave sessions with the
-noatomsautoload option would be useful].

_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users
Samuel GOUGEON Samuel GOUGEON
Reply | Threaded
Open this post in threaded view
|

Re: test_run failed: Slave Scilab exited with error code 127

Le 01/08/2019 à 22:49, Samuel Gougeon a écrit :
Le 01/08/2019 à 22:16, philippe a écrit :
...

no all tests fail (excepts those who are skipped automatically) :


This could come from an autoloaded ATOMS module, if any.
You may try canceling the autoloading of all your installed modules, and then rerun test_run.

[a new test_run() option running all slave sessions with the -noatomsautoload option would be useful].


Reported as bug 16161. Thanks for this opportunity to improve test_run().



_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users
Philippe Roux Philippe Roux
Reply | Threaded
Open this post in threaded view
|

Re: test_run failed: Slave Scilab exited with error code 127

In reply to this post by Samuel GOUGEON
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

Philippe

_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users
Philippe Roux Philippe Roux
Reply | Threaded
Open this post in threaded view
|

Re: test_run failed: Slave Scilab exited with error code 127

In reply to this post by Samuel GOUGEON
Le 01/08/2019 à 23:28, Samuel Gougeon a écrit :
> Le 01/08/2019 à 22:49, Samuel Gougeon a écrit :
>> Le 01/08/2019 à 22:16, philippe a écrit :
>>> ...
>>>
>>> no all tests fail (excepts those who are skipped automatically) :
>>
>>
>> This could come from an autoloaded ATOMS module, if any.

this happened on a "fresh install" so with no ATOMS module loaded.

>> You may try canceling the autoloading of all your installed modules,
>> and then rerun test_run.

I used AtomsQuit()  and rerun test_run  but that has no effect.

>
>
> Reported as bug 16161
> <http://bugzilla.scilab.org/show_bug.cgi?id=16161>. Thanks for this
> opportunity to improve test_run().


Thanks samuel!

_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users
Samuel GOUGEON Samuel GOUGEON
Reply | Threaded
Open this post in threaded view
|

Re: test_run failed: Slave Scilab exited with error code 127

In reply to this post by Philippe Roux
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.



_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users
Philippe Roux Philippe Roux
Reply | Threaded
Open this post in threaded view
|

Re: test_run failed: Slave Scilab exited with error code 127

Le 02/08/2019 à 16:27, Samuel Gougeon a écrit :

>
> 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.

I've just done this an get :


-> test_run("ast",[],"no_check_ref")
    TMPDIR = /tmp/SCI_TMP_32597_VRKa5r

  Module  001/001 - [ast] :

  001/154 - [ast] Sand.........................................
  (   /usr/-6.0.2//bin/scilab -nwni  -nb -quit --timeout 15m  -f
/tmp/SCI_TMP_32597_VRKa5r/Sand.tst > /tmp/SCI_TMP_32
  597_VRKa5r/Sand.res ) 2> /tmp/SCI_TMP_32597_VRKa5r/Sand.er


the command line "/usr/-6.0.2//bin/scilab"  should be instead :
/usr/share/scilab-6.0.2/bin/scilab

the problem seems to come from line 811

if (getos() <> "Windows") & ~isfile(SCI+"/bin/scilab") then
         SCI_BIN = strsubst(SCI,"share/scilab","");//<---line 811
     else
         SCI_BIN = SCI;
     end

there is two occurrences of "share/scilab" in the path so the
substitution is not valid :


--> SCI
  SCI  =

  /usr/share/scilab-6.0.2/share/scilab

the line 811 should be replaced with something like :

SCI_path=strsplit(SCI,'/');SCI_BIN = strcat(SCI_path(1:$-2),'/');

but this modification freeze scilab when launching test_run although
running "/usr/share/scilab-6.0.2/bin/scilab -nwni  -nb -quit --timeout
15m  -f /tmp/SCI_TMP_32597_VRKa5r/Sand.tst"  from a terminal is ok ...?

Thanks a lot Samuel for the help, do you want me to add a bug report ?

Philippe

_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users
Samuel GOUGEON Samuel GOUGEON
Reply | Threaded
Open this post in threaded view
|

Re: test_run failed: Slave Scilab exited with error code 127

Le 06/08/2019 à 15:03, philippe a écrit :
.../...
I've just done this an get :


-> test_run("ast",[],"no_check_ref")
   TMPDIR = /tmp/SCI_TMP_32597_VRKa5r

 Module  001/001 - [ast] :

 001/154 - [ast] Sand.........................................
 (   /usr/-6.0.2//bin/scilab -nwni  -nb -quit --timeout 15m  -f /tmp/SCI_TMP_32597_VRKa5r/Sand.tst > /tmp/SCI_TMP_32
 597_VRKa5r/Sand.res ) 2> /tmp/SCI_TMP_32597_VRKa5r/Sand.er


the command line "/usr/-6.0.2//bin/scilab"  should be instead :
/usr/share/scilab-6.0.2/bin/scilab

the problem seems to come from line 811

if (getos() <> "Windows") & ~isfile(SCI+"/bin/scilab") then
        SCI_BIN = strsubst(SCI,"share/scilab","");//<---line 811
    else
        SCI_BIN = SCI;
    end

there is two occurrences of "share/scilab" in the path so the substitution is not valid :


--> SCI
 SCI  =

 /usr/share/scilab-6.0.2/share/scilab


If this path specific to your installation? I mean, some other Linux or oMacOS users run tests without this issue.
Anyway, this has to be fixed.


the line 811 should be replaced with something like :

SCI_path=strsplit(SCI,'/');SCI_BIN = strcat(SCI_path(1:$-2),'/');

but this modification freeze scilab when launching test_run although running "/usr/share/scilab-6.0.2/bin/scilab -nwni  -nb -quit --timeout 15m  -f /tmp/SCI_TMP_32597_VRKa5r/Sand.tst"  from a terminal is ok ...?

Have you checked that this is actually the run command, with the same disp spy instruction?
If yes, then there may be 2 another bug after the first one.



Thanks a lot Samuel for the help, do you want me to add a bug report ?


Yes please. It will need your contribution to test and valid the solution.
It will be hard (and heavy) to get a specific scilab installation to test the patch.


Samuel


_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users
Samuel GOUGEON Samuel GOUGEON
Reply | Threaded
Open this post in threaded view
|

Re: test_run failed: Slave Scilab exited with error code 127

In reply to this post by Philippe Roux
Le 06/08/2019 à 15:03, philippe a écrit :

> .../...
> I've just done this an get :
>
>
> -> test_run("ast",[],"no_check_ref")
>    TMPDIR = /tmp/SCI_TMP_32597_VRKa5r
>
>  Module  001/001 - [ast] :
>
>  001/154 - [ast] Sand.........................................
>  (   /usr/-6.0.2//bin/scilab -nwni  -nb -quit --timeout 15m  -f
> /tmp/SCI_TMP_32597_VRKa5r/Sand.tst > /tmp/SCI_TMP_32
>  597_VRKa5r/Sand.res ) 2> /tmp/SCI_TMP_32597_VRKa5r/Sand.er
>
>
> the command line "/usr/-6.0.2//bin/scilab"  should be instead :
> /usr/share/scilab-6.0.2/bin/scilab

.../...

>
> --> SCI
>  SCI  =
>
>  /usr/share/scilab-6.0.2/share/scilab


So, shouldn't the command line be
/usr/share/scilab-6.0.2/share/scilab/bin/scilab
intead of
/usr/share/scilab-6.0.2/bin/scilab
that you mention earlier?

Could you confirm please?
Thanks

_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users
Samuel GOUGEON Samuel GOUGEON
Reply | Threaded
Open this post in threaded view
|

Re: test_run failed: Slave Scilab exited with error code 127

Le 06/08/2019 à 15:44, Samuel Gougeon a écrit :
Le 06/08/2019 à 15:03, philippe a écrit :
.../...
I've just done this an get :


-> test_run("ast",[],"no_check_ref")
   TMPDIR = /tmp/SCI_TMP_32597_VRKa5r

 Module  001/001 - [ast] :

 001/154 - [ast] Sand.........................................
 (   /usr/-6.0.2//bin/scilab -nwni  -nb -quit --timeout 15m  -f /tmp/SCI_TMP_32597_VRKa5r/Sand.tst > /tmp/SCI_TMP_32
 597_VRKa5r/Sand.res ) 2> /tmp/SCI_TMP_32597_VRKa5r/Sand.er


the command line "/usr/-6.0.2//bin/scilab"  should be instead :
/usr/share/scilab-6.0.2/bin/scilab

.../...


--> SCI
 SCI  =

 /usr/share/scilab-6.0.2/share/scilab


So, shouldn't the command line be
/usr/share/scilab-6.0.2/share/scilab/bin/scilab
intead of
/usr/share/scilab-6.0.2/bin/scilab
that you mention earlier?


OK, i have got it. Your binary is actually  in /usr/share/scilab-6.0.2/bin/scilab
This is why this "if" condition is useful in this case.
But still, if a standard installation is always done with this path starting with /usr/share/scilab-6.0.2, then the bug should occur for every Linux or Darwin user (with no binary located where expected in first), unless it is a patch that has never been tested...



_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users
Philippe Roux Philippe Roux
Reply | Threaded
Open this post in threaded view
|

Re: test_run failed: Slave Scilab exited with error code 127

In reply to this post by Samuel GOUGEON
Le 06/08/2019 à 15:44, Samuel Gougeon a écrit :

>
>
> So, shouldn't the command line be
> /usr/share/scilab-6.0.2/share/scilab/bin/scilab
> intead of
> /usr/share/scilab-6.0.2/bin/scilab
> that you mention earlier?
>
> Could you confirm please?



for ubuntu 18.04 current scilab version is 6.0.1  so I've donwloaded
scilab-6.0.2.bin.linux-x86_64.tar.gz from scilab website and

gunzip  scilab-6.0.2.bin.linux-x86_64.tar.gz
tar -xvf scilab-6.0.2.bin.linux-x86_64.tar
mv scilab-6.0.2/ /usr/share/

the structure of /usr/share/scilab/ and /usr/share/scilab-6.0.2/  is
different

$ls /usr/share/scilab/ /usr/share/scilab-6.0.2/
/usr/share/scilab/:
ACKNOWLEDGEMENTS  contrib  COPYING-BSD  etc  modules  tools  Version.incl

/usr/share/scilab-6.0.2/:
ACKNOWLEDGEMENTS  bin  CHANGES.md  COPYING  include  lib  README.md
share  thirdparty

scilab-6.0.2 launch command is located in bin/

$ls /usr/share/scilab-6.0.2/bin/
modelicac  modelicat  scilab  scilab-adv-cli  scilab-bin  scilab-cli
scilab-cli-bin  scinotes  xcos  XML2Modelica

Philippe

_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users
Philippe Roux Philippe Roux
Reply | Threaded
Open this post in threaded view
|

Re: test_run failed: Slave Scilab exited with error code 127

In reply to this post by Samuel GOUGEON
Le 06/08/2019 à 15:38, Samuel Gougeon a écrit :

> Le 06/08/2019 à 15:03, philippe a écrit :
>>
>> the line 811 should be replaced with something like :
>>
>> SCI_path=strsplit(SCI,'/');SCI_BIN = strcat(SCI_path(1:$-2),'/');
>>
>> but this modification freeze scilab when launching test_run although
>> running "/usr/share/scilab-6.0.2/bin/scilab -nwni  -nb -quit --timeout
>> 15m  -f /tmp/SCI_TMP_32597_VRKa5r/Sand.tst"  from a terminal is ok ...?
>
> Have you checked that this is *actually* the run command, with the same
> disp spy instruction?

yes I copied the command from scilab terminal (frozen)  and ran it in
another terminal (bash).

> If yes, then there may be 2 another bug after the first one.
> >
>>
>> Thanks a lot Samuel for the help, do you want me to add a bug report ?
>
>
> Yes please. It will need your contribution to test and valid the solution.
> It will be hard (and heavy) to get a specific scilab installation to
> test the patch.

bug 16168 :

http://bugzilla.scilab.org/show_bug.cgi?id=16168

best regards
Philippe

_______________________________________________
users mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/users