Lava xml-rpc notification machnism, criteria.status indicates which event can be notified to user (by hook callback). But the criteria.status only has such as "Complete Incomplete,Canceled,finished" events. Why the lava is not designed a machnism that notify user when only a test case is complete(err..),if so that user has more rights to control test process execution.
hi all
i add a worker to master from the slave container by lavacli..,
But the worker is offline in the localhost:10080 web .
Master and slave can ping each other sucessfully.
any guy konw why?
THX
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):
Hello,
When trying to use lavacli to add a remote worker, it works fine if
the user is a superuser. However, if I drop the superuser privileges
and add just the privileges for adding workers, it fails with:
Unable to call 'workers.add': <Fault 403: "User 'testuser' is not superuser."
we even tried enabling all the permissions for that user, but leaving
the superuser flag off, and it still fails.
Why does this require superuser and the specific permissions related
to workers don't work?
Kevin