https://validation.linaro.org/static/docs/v2/glossary.html#term-multinodehttps://validation.linaro.org/static/docs/v2/multinode.html
it said "A single test job which runs across multiple devices".
I still don't quite understandt the purpose of MultiNode. Is that mean
that a single test job's all test cases are parallel executed
simultaneously on multiple devices?
For example it have 10 test cases and 5 devices, when job is running,
firstly the former 5 cases is distributed to 5 devices and parallel run
(case 1 is run on device 1,case 2 is run on device 2,... device 5 is run on
device 5). When a case is end(suppose case 2) ,then case 6 is scheduled to
run on device 2... and so on.Is my understanding correct?
I want to implement a function: When a test case in job is crush or return err(no zero), the job can be rescheduled(or resubmit). Does it need to write own event notification? Need monitor "job Incomplete" action?
In addition, according to lava xmlrpc doc, I input command in lava server console: python zmq_client.py -j 121 --hostname tcp://127.0.0.1:5500 -t 1200 .The was error :
....
File "/usr/lib/python2.7/httplib.py", line 821, in connect
self.timeout, self.source_address)
File "/usr/lib/python2.7/socket.py", line 557, in create_connection
for res in getaddrinfo(host, port, 0, SOCK_STREAM):
In lava website,it is lack the documents on how to build multiple remote slave test system.For example,if our system has a lot of test devices.
What are the general design principles about how to plan to deploy remote workers, how many dut connect to one worker,etc.
Is there any background knowledges about multiple slave and multiNode?
The board has usb serial, it connected to computer running dispatcher. On dispatcher computer that usb serial device name is /dev/ttyUSB0 .
How to configure usb serial in device .jinja2 file?
Hello Lava users,
Do you have any example or advice to share on a way to measure boot time using Lava?
Let's say that I use u-boot, a minimal boot for a device running Linux, and I want to measure the time spent between Power On (pdu-reboot e.g) and Linux prompt.
Best regards,
Denis
Hi Team,
Do you know how to fix below issue when I trigger one LAVA job on LAVA V2 server?
Traceback (most recent call last):
File "trigger.py", line 184, in <module>
main(sys.argv[1:])
File "trigger.py", line 174, in main
lava_bn = lava_server.submit_job(lava_jd)
* File "trigger.py", line 52, in submit_job*
return self._server.scheduler.submit_job(job_data)
File "/usr/lib/python3.5/xmlrpc/client.py", line 1092, in _call_
return self._send(self._name, args)
File "/usr/lib/python3.5/xmlrpc/client.py", line 1432, in __request
verbose=self.__verbose
File "/usr/lib/python3.5/xmlrpc/client.py", line 1134, in request
return self.single_request(host, handler, request_body, verbose)
File "/usr/lib/python3.5/xmlrpc/client.py", line 1150, in single_request
return self.parse_response(resp)
File "/usr/lib/python3.5/xmlrpc/client.py", line 1322, in parse_response
return u.close()
File "/usr/lib/python3.5/xmlrpc/client.py", line 655, in close
raise Fault(**self._stack[0])
xmlrpc.client.Fault: <Fault -32603: 'Internal Server Error (contact server administrator for details): relation "lava_scheduler_app_build" does not exist\nLINE 1: ...number", "lava_scheduler_app_build"."branch" FROM "lava_sche...\n
Best Regards
Zhanghui Yuan
OTC Production Kernel Integration Test
Refer to https://validation.linaro.org/scheduler/job/1890179,I had run a test case in real board successfully
The nfsrootfs image is too big ,it took too many download time in every test. So I put kernel nfs and dtb image files on tftp server, then delete deploy action and add a few boot action commands to specify tftp addr... The parameters(login_prompt&usrname&prompts) of the boot action are same with success version(has deploy action):
...
- boot:
connection: telnet localhost 7000
method: u-boot
##note the fellow commands lines is new added,the success version(has deploy action)that commands line is only "commands:nfs"
commands:
- setenv serverip 192.168.1.5
- tftp 0x8...0000 zImage_arm_1
- tftp 0x4...0000 dtb_arm_1
- setenv nfsroot rootfs_1
- boot
auto_login:
login_prompt: "arm login:"
username: root
prompts:
- root@arm:~#
timeout:
minutes: 3
...
After job submited,the log display that kernel startup and rootfs mount ok, but it always failed at login error.
error log lines:
err info:lava-test-shell: Wait for prompt ['root@arm:~#', 'Login incorrect', 'Login timed out', 'lava-test: # '] (timeout 00:05:00)
Nothing to run. Maybe the 'deploy' stage is missing, otherwise this is a bug which should be reported.
In addition, does the uboot prompts(u-boot=>) no need to describe in boot action section? In other words the prompts auto_login is only described for kernel?