On Mon, 18 Jul 2016 19:22:31 +0000 "Albarran, Josue" j-albarran@ti.com wrote:
My NFS root does in fact have /bin/bash.
OK, that should be fine - as long as unpacking the NFS using tar -xzf does produce ./bin/bash, not ./somedirectory/bin/bash
Could you please clarify the lava test running process? Lava is sending this command "/lava-188/bin/lava-test-runner /lava-188" to the board shell itself.
Exactly. LAVA is using the serial console to issue commands.
The overlay is put into a directory called /lava-<jobid> inside the NFS root.
The overlay contains a lava-test-runner script which takes the directory as the argument.
The script is built from the data in the overlay.
The overlay itself will exist (temporarily) in your /tmp/ location. e.g. for job 9999 /tmp/lava-dispatcher/slave/9999/logs/
You can see the files in that using tar -tzf.
There's also an err file in the directory above.
As I've mentioned before, *please* start with the standard test job - without alterations - and *then* make one change at a time. That's why we've prepared standard jobs like this. e.g. use the standard kernel, modules & dtb with your NFS and your kernel & dtb with the standard NFS. Do each of those changes with the standard test definition, then substitute in your own. You can also sign up for a linaro account and request permission to submit jobs to staging.validation.linaro.org which is running the release candidate for 2016.7 and may be easier to follow in the logs. Using staging also means that others can check the actual files you are using and everyone is looking at the same log files.
This http://pastebin.ubuntu.com/19938573/ is the deploy stage of the complete log.
Thanks,
Josue
-----Original Message----- From: Neil Williams [mailto:codehelp@debian.org] Sent: Monday, July 18, 2016 1:53 PM To: Albarran, Josue Cc: linaro-validation@lists.linaro.org Subject: Re: [Linaro-validation] lava-test-case
On Mon, 18 Jul 2016 15:33:33 +0000 "Albarran, Josue" j-albarran@ti.com wrote:
Hi,
I'm trying to run a simple lava-test-case from a test definition I defined and I get the "lava-test-shell timed out" error message.
This is just a message showing the length of the current timeout: lava-test-shell.log test shell timeout: 300 seconds
So, it's not a timeout, there is a missing file:
/lava-188/bin/lava-test-runner: No such file or directory
Shell can be awkward with these errors - is it possible that your NFS root lacks /bin/bash ?
The interpreter to use is dictated by the deployment_data: https://git.linaro.org/lava/lava-dispatcher.git/blob/3377ef1c8ffa53123dc4f7d...
You've specified debian, so /bin/bash needs to exist. If your image is not actually debian, you should specify oe for OpenEmbedded which looks for /bin/sh
Is there something I'm missing here? I'm attaching the job definition, test definition, and test log.
Job definition: http://pastebin.ubuntu.com/19906000/ Test definition: http://pastebin.ubuntu.com/19906153/ Test log: http://pastebin.ubuntu.com/19904627/
Is that just the summary log? There will be more information in the Complete Log, especially the deploy stage.
Compare with this job: https://validation.linaro.org/scheduler/job/1019247/complete_log?section=dep...
Test definition: http://pastebin.ubuntu.com/19906153/
The quotes are unnecessary in the first line.
--
Neil Williams