Hi,all:
If devive have boot successed，can I skip deploy and boot step in job.yaml?
This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you.
Hello LAVA experts,
I am currently working with LAVA and was asked to find is there a way to get data from device dictionary inside a running job. Details like below:
I have a device name demo-01, and its device-dictionary have one line like "{% set my_property = 'my_prop' %}". Then I have a job running on demo-01 device, and I would like to use string 'my_prop' to passed into a script during running. Is it possible to get device-dictionary data directly from job definition(Job Submitter webpage) or test definition(yaml file)? If yes, how could I do this? If not, is there any good way you would like to share to solve this problem?
Thanks and Best Regards,
Yifan
Hi all,
Is there any limitation on test duration when using LAVA to do tests?
Recently, I found my tests were automatically canceled after running for 24 hours and I could not find any clue about why the job was canceled. Can anybody give me some help?
(Very sorry my LAVA version is V1.)
12794.0 <LAVA_DISPATCHER>2017-06-25 02:31:42 PM INFO: Cancel operation
12794.1 <LAVA_DISPATCHER>2017-06-25 02:31:42 PM DEBUG: finally status fail
12794.2 <LAVA_DISPATCHER>2017-06-25 02:31:42 PM WARNING: [ACTION-E] boot_image is finished with error (Cancel).
12794.3 <LAVA_DISPATCHER>2017-06-25 02:31:42 PM WARNING: Target : power_off being call
Thanks.
Hi,
We've hit an issue when running lava-master on Debian Jessie and
lava-slave on Debian Stretch, after a few minutes the slave would
stop working. After some investigation, it turned out to be due
to a difference of the libzmq versions in Jessie (4.0.5+dfsg-2)
and Stretch (4.2.1-4) causing some protocol errors.
The line that detects the error in Stretch is:
https://github.com/zeromq/libzmq/blob/7005f22726d4a6ca527f27560a0a132394fdb…
This appears to be due to how the "once" counter gets written
into memory and into the zmq packets: the libzmq version from
Jessie uses memcpy whereas the one in Stretch calls put_uint64.
As a result the byte endianness has changed from little to big,
causing the packets to work until "once" reaches 255 which
translates into 0xff << 56, after which it overflows to 0 and
causes the error.
This is not a LAVA bug as such, rather a libzmq one, but it
impacts interoperability between Jessie and Stretch for LAVA so
it may need to be documented or resolved somehow. We've
installed the new version of libzmq onto our Jessie servers to
align them with Stretch; doing this does fix the problem.
Best wishes,
Guillaume
Hi All,
We have a Lab and the DUTs in the Lab will be used for both automation testing(LAVA) and manual usage(development, debug, manual testing).
And we will develop a tool for the manual usage, please find the basic requirements of the tool in the attachment.
I list possible solutions about how to develop the lab tool and let the tool cooperate with LAVA on the same Lab hardwares. which one is better? could you give your suggestions?
1. Develop the lab tool based on LAVA framawork.
Need to modify LAVA DB: add some new tables for network ports, port attribution, port connection, usage log, notes, also need to add columns to existing tables lava_scheduler_app_device.
Need to modify LAVA command line, add functions like lava-server reserve dut1, lava-server connect dut1.
Need to add new codes for the features which LAVA doesn't support, part of codes may be reused, I need to look into LAVA and check how to reuse them.
The tool will be developed based on https://github.com/Linaro/lava-server and will be installed on LAVA master, right?
Most probably we will maintain the codes change in local repository because it is difficult to upstream thousands of codes changes to linaro master repository. We need to merge the changes in master repository to local repository.
2. Develop the lab tool as a separated tool and use separated DB. There are two ways to avoid the DUT conflicts between the lab tool and LAVA:
a) Lab tool DB maintain all DUTs, LAVA DB also maintain all DUTs, when a user want to do automation testing on one DUT, he need to reserve this DUT via lab tool in advance, then he can run automation testing on the specified DUT.
b),Divide the DUTs to two groups, one group is for automation testing and it will be added to LAVA DB, the other one group is for manual usage and will be added to lab tool DB.
Another question about how to link/unlink two network ports dynamically(see requirement#7 in attachment) in automation testing. I am not sure whether LAVA can support this feature later, the simple way is supporting it in test script:
Do the link/unlink in test script: subprocess.Popen(["lab-tool","link","dut1.eth_1g_1","dut2.eth_1g_1"]) , and test script needs to get DUT name from LAVA in advance.
Does this work?
BR
Yongtao
This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you.
Hi,
I am trying to run a multinode test job
<https://staging.validation.linaro.org/scheduler/job/175378/definition> in
LAVA v2.
It failed <https://staging.validation.linaro.org/scheduler/job/175378#L555>.
After
a short discussion with Chase, I realized if I want to run multinode test
job I have to use "lava-multinode" protocol.
However, I still need "lava-lxc" to deploy the test image for hikey.
I am wondering if it is possible to use two protocols, lava-lxc for
deployment test image and lava-multinode to run the test, in the same test
job?
If yes, could you please provide some examples?
Thanks,
Arthur
Hi ,
I known can add the device_tags by the web , and if i can add the device_tags by the cmdline ?
Best Regards
XuHongyu
This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you.
Hello，Neil：
1.Can you give me a deploy flow for a x86 device .
2．I want to use web UI submit job for one time N jobs. (N>10)
How can I do it?
Thanks.
Amanda
This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you.
Hi all,
Can be used multi database in the lava ? And is there any introduction to this ?
Best Regards
XuHongyu
This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you.
Hi,
Someone with the nickname "Nurav" pinged in #linaro-lava IRC channel
last week regarding installation problem to install lava in jessie using
the jessie-backports repository. The person also diligently followed up
with me to check what is wrong with his/her installation on private
messages. I did find sometime to do the testing today. Since, I do not
know any contact details of 'Nurav' I am writing my findings here, based
on lava installation I did on fresh jessie containers, hopefully the
person is available in this mailing list and will see this message.
The fresh installation went fine with both jessie and also using jessie
backports and LAVA production-repo. I ve put up the complete log of the
installations I tried in the following files:
* Fresh installation of lava from jessie-backports -
http://people.linaro.org/~senthil.kumaran/logs/lava-jessie-bp-installation.…
* Installing 2017.5 lava from jessie to jessie-backports to
production-repo -
http://people.linaro.org/~senthil.kumaran/logs/lava-jessie-bp-installation-…
HTH. Thank You.
--
Senthil Kumaran
http://www.stylesen.org/http://www.sasenthilkumaran.com/
