[Fuego] Functional.LTP failed with "./ltp_target_run.sh not found"

Daniel Sangorrin daniel.sangorrin at toshiba.co.jp
Wed Oct 11 05:26:23 UTC 2017


> -----Original Message-----
> From: fuego-bounces at lists.linuxfoundation.org [mailto:fuego-bounces at lists.linuxfoundation.org] On Behalf Of Liu, Wenlong
> Sent: Wednesday, October 11, 2017 2:10 PM
> To: Bird, Timothy; fuego at lists.linuxfoundation.org
> Subject: Re: [Fuego] Functional.LTP failed with "./ltp_target_run.sh not found"
> 
> Hi Tim,
> 
> > Have you run Functional.LTP with the 'buildonly' spec yet?
> > This should deploy the ltp_target_run.sh script to the target.
> > Then you can execute other specs.
> >
> > We should probably put something in the test_pre_check for LTP, when
> > "runonly" is true, to check that LTP has previously been deployed to the
> > target.  Checking for ltp_target_run.sh might just do the trick.
> I know what you mean, but the LTP is already installed on my target board(build and deploy are not necessary for me).
> The LTP is already installed when the rootfs is made.

This works as follows:
- buildonly: produces a patched version of LTP, builds it and generates a tar.gz file that you have to install in your target rootfs.
- runonly: skips build and deploy, and runs the LTP binaries that you installed on the target rootfs.

Non-patched versions of LTP are not supported by the parser.

Thanks,
Daniel

> > -----Original Message-----
> > From: Bird, Timothy [mailto:Tim.Bird at sony.com]
> > Sent: Wednesday, October 11, 2017 12:46 PM
> > To: Liu, Wenlong/刘 文龙 <liuwl.fnst at cn.fujitsu.com>;
> > fuego at lists.linuxfoundation.org
> > Subject: RE: Functional.LTP failed with "./ltp_target_run.sh not found"
> >
> >
> >
> > > -----Original Message-----
> > > From: Liu, Wenlong on Sunday, October 08, 2017 7:17 PM Hi,
> > >
> > > When using feature "runonly" for LTP test, something like below, ...
> > >         "can": {
> > >             "tests": "can",
> > >             "runonly": "true",
> > >             "runfolder": "/opt/ltp",
> > >             "extra_success_links": {"xlsx": "results.xlsx"}
> > >         },
> > > ...
> > > the test will be failed.
> > >
> > > The cause of the problem might be as below, LTP test deploy will be
> > > skipped when using "runonly" for testing, but ltp_target_run.sh should
> > > be exceptional.
> > >
> > > [Console Log]
> > > ...
> > > + report 'cd /opt/ltp; TESTS="can "; PTSTESTS=""; RTTESTS=""; .
> > > ./ltp_target_run.sh'
> > > + is_empty cd '/opt/ltp;' 'TESTS="can' '";' 'PTSTESTS="";'
> > 'RTTESTS="";' .
> > > ./ltp_target_run.sh
> > > + '[' -z cd ']'
> > > + RETCODE=/tmp/20402-24740
> > > + cmd 'touch /tmp/20402-24740'
> > > + report_devlog 'cmd: touch /tmp/20402-24740'
> > > + echo 'cmd: touch /tmp/20402-24740'
> > > + ov_transport_cmd 'touch /tmp/20402-24740'
> > > + case "$TRANSPORT" in
> > > + sshpass -e ssh -o ServerAliveInterval=30 -o StrictHostKeyChecking=no
> > > + -o
> > > UserKnownHostsFile=/dev/null -o LogLevel=error -o ConnectTimeout=30 -p
> > > 22 root at 192.168.10.6 'touch /tmp/20402-24740'
> > > + '[' -z ']'
> > > + echo 'WARNING: test log file parameter empty, so will use default'
> > > WARNING: test log file parameter empty, so will use default
> > > + safe_cmd '{ cd /opt/ltp; TESTS="can "; PTSTESTS=""; RTTESTS=""; .
> > > ./ltp_target_run.sh; echo $? > /tmp/20402-24740; } 2>&1 | tee
> > > /home/a/fuego.Functional.LTP/Functional.LTP.log'
> > > + ov_rootfs_oom
> > > + cmd 'echo 1000 > /proc/$$/oom_score_adj'
> > > + report_devlog 'cmd: echo 1000 > /proc/$$/oom_score_adj'
> > > + echo 'cmd: echo 1000 > /proc/$$/oom_score_adj'
> > > + ov_transport_cmd 'echo 1000 > /proc/$$/oom_score_adj'
> > > + case "$TRANSPORT" in
> > > + sshpass -e ssh -o ServerAliveInterval=30 -o StrictHostKeyChecking=no
> > > + -o
> > > UserKnownHostsFile=/dev/null -o LogLevel=error -o ConnectTimeout=30 -p
> > > 22 root at 192.168.10.6 'echo 1000 > /proc/$$/oom_score_adj'
> > > + cmd '{ cd /opt/ltp; TESTS="can "; PTSTESTS=""; RTTESTS=""; .
> > > ./ltp_target_run.sh; echo $? > /tmp/20402-24740; } 2>&1 | tee
> > > /home/a/fuego.Functional.LTP/Functional.LTP.log'
> > > + report_devlog 'cmd: { cd /opt/ltp; TESTS="can "; PTSTESTS="";
> > RTTESTS=""; .
> > > ./ltp_target_run.sh; echo $? > /tmp/20402-24740; } 2>&1 | tee
> > > /home/a/fuego.Functional.LTP/Functional.LTP.log'
> > > + echo 'cmd: { cd /opt/ltp; TESTS="can "; PTSTESTS=""; RTTESTS=""; .
> > > ./ltp_target_run.sh; echo $? > /tmp/20402-24740; } 2>&1 | tee
> > > /home/a/fuego.Functional.LTP/Functional.LTP.log'
> > > + ov_transport_cmd '{ cd /opt/ltp; TESTS="can "; PTSTESTS="";
> > RTTESTS=""; .
> > > ./ltp_target_run.sh; echo $? > /tmp/20402-24740; } 2>&1 | tee
> > > /home/a/fuego.Functional.LTP/Functional.LTP.log'
> > > + case "$TRANSPORT" in
> > > + sshpass -e ssh -o ServerAliveInterval=30 -o StrictHostKeyChecking=no
> > > + -o
> > > UserKnownHostsFile=/dev/null -o LogLevel=error -o ConnectTimeout=30 -p
> > > 22 root at 192.168.10.6 '{ cd /opt/ltp; TESTS="can "; PTSTESTS="";
> > RTTESTS=""; .
> > > ./ltp_target_run.sh; echo $? > /tmp/20402-24740; } 2>&1 | tee
> > > /home/a/fuego.Functional.LTP/Functional.LTP.log'
> > > sh: ./ltp_target_run.sh: No such file or directory ...
> >
> > Have you run Functional.LTP with the 'buildonly' spec yet?
> > This should deploy the ltp_target_run.sh script to the target.
> > Then you can execute other specs.
> >
> > We should probably put something in the test_pre_check for LTP, when
> > "runonly" is true, to check that LTP has previously been deployed to the
> > target.  Checking for ltp_target_run.sh might just do the trick.
> >
> > I'll try to take a look at this tomorrow.  Sorry I didn't get to it today,
> > as I was busy setting up the new Fuego web site (among other things).
> >
> > Thanks very much for the report.
> >  -- Tim
> >
> >
> 
> 
> 
> _______________________________________________
> Fuego mailing list
> Fuego at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/fuego




More information about the Fuego mailing list