Hi, In LAVA v1, as I remember, I can use either "device" or "device_type" to request a device for the test. If I use "device", for example "device": "beaglebone-black03", then the specific device, beaglebone-black03, will be used for the test. Can I do the same thing in LAVA v2? To request a device by using device name?
Thanks, Arthur
On Thu, Aug 10, 2017 at 10:55:32AM -0700, Arthur She wrote:
Hi, In LAVA v1, as I remember, I can use either "device" or "device_type" to request a device for the test. If I use "device", for example "device": "beaglebone-black03", then the specific device, beaglebone-black03, will be used for the test. Can I do the same thing in LAVA v2? To request a device by using device name?
Hi Arthur,
No, it is a deliberate design decision in LAVA v2 to *not* do things that way. What are you trying to do that needs you to use a specific device? If there's special hardware attached (for example), then you could use device tags to manage that choice.
Cheers,
Hi Steve, Since 4k hdmi dongles had been deployed to staging HiKey 01, 03, 04 and staging db410c-01 (CTT-288 https://projects.linaro.org/browse/CTT-288). I'd like to run some tests with these devices to verify the hardware. The only way that I can think of is to submit a bunch of test jobs with tag '4k-hdmi-dongle'.
Do you have any better ideas?
Thanks, Arthur
2017-08-10 11:04 GMT-07:00 Steve McIntyre steve.mcintyre@linaro.org:
On Thu, Aug 10, 2017 at 10:55:32AM -0700, Arthur She wrote:
Hi, In LAVA v1, as I remember, I can use either "device" or "device_type" to request a device for the test. If I use "device", for example "device": "beaglebone-black03", then the specific device, beaglebone-black03, will be used for the test. Can I do the same thing in LAVA v2? To request a device by using device
name?
Hi Arthur,
No, it is a deliberate design decision in LAVA v2 to *not* do things that way. What are you trying to do that needs you to use a specific device? If there's special hardware attached (for example), then you could use device tags to manage that choice.
Cheers,
Steve McIntyre steve.mcintyre@linaro.org http://www.linaro.org/ Linaro.org | Open source software for ARM SoCs
On 10 August 2017 at 15:11, Arthur She arthur.she@linaro.org wrote:
Hi Steve, Since 4k hdmi dongles had been deployed to staging HiKey 01, 03, 04 and staging db410c-01 (CTT-288). I'd like to run some tests with these devices to verify the hardware.
The only way that I can think of is to submit a bunch of test jobs with tag '4k-hdmi-dongle'.
That *is* the documented way to do this - the device tag was created & applied solely for this purpose.
Do you have any better ideas?
Why would using the device tag be a problem?
Thanks, Arthur
2017-08-10 11:04 GMT-07:00 Steve McIntyre steve.mcintyre@linaro.org:
On Thu, Aug 10, 2017 at 10:55:32AM -0700, Arthur She wrote:
Hi, In LAVA v1, as I remember, I can use either "device" or "device_type" to request a device for the test. If I use "device", for example "device": "beaglebone-black03", then the specific device, beaglebone-black03, will be used for the test. Can I do the same thing in LAVA v2? To request a device by using device name?
Hi Arthur,
No, it is a deliberate design decision in LAVA v2 to *not* do things that way. What are you trying to do that needs you to use a specific device? If there's special hardware attached (for example), then you could use device tags to manage that choice.
Cheers,
Steve McIntyre steve.mcintyre@linaro.org http://www.linaro.org/ Linaro.org | Open source software for ARM SoCs
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Hi Neil, Steve, Thanks for your response.
2017-08-15 1:32 GMT-07:00 Neil Williams neil.williams@linaro.org:
On 10 August 2017 at 15:11, Arthur She arthur.she@linaro.org wrote:
Hi Steve, Since 4k hdmi dongles had been deployed to staging HiKey 01, 03, 04 and staging db410c-01 (CTT-288). I'd like to run some tests with these devices to verify the hardware.
The only way that I can think of is to submit a bunch of test jobs with
tag
'4k-hdmi-dongle'.
That *is* the documented way to do this - the device tag was created & applied solely for this purpose.
Do you have any better ideas?
Why would using the device tag be a problem?
There is no problem at all. The device tag is good and I know my case is not usual. I just want to know if there is a way that can make sure every device would be tested. Think about this case, if there are already many test jobs with different complexity in queue. If I submit a bunch of test jobs, the situation might be some of devices might run the test job multiple times and some of them might not even get one. Anyway, my problem solved. I am lucky enough, I submitted 3 test jobs and every hikey with 4k hdmi dongle got one.
Thanks, Arthur
Thanks, Arthur
2017-08-10 11:04 GMT-07:00 Steve McIntyre steve.mcintyre@linaro.org:
On Thu, Aug 10, 2017 at 10:55:32AM -0700, Arthur She wrote:
Hi, In LAVA v1, as I remember, I can use either "device" or "device_type"
to
request a device for the test. If I use "device", for example "device": "beaglebone-black03", then the specific device, beaglebone-black03, will be used for the test. Can I do the same thing in LAVA v2? To request a device by using device name?
Hi Arthur,
No, it is a deliberate design decision in LAVA v2 to *not* do things that way. What are you trying to do that needs you to use a specific device? If there's special hardware attached (for example), then you could use device tags to manage that choice.
Cheers,
Steve McIntyre steve.mcintyre@linaro.org http://www.linaro.org/ Linaro.org | Open source software for ARM SoCs
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
Hey Arthur,
On Tue, Aug 15, 2017 at 10:43:12AM -0700, Arthur She wrote:
2017-08-15 1:32 GMT-07:00 Neil Williams neil.williams@linaro.org:
On 10 August 2017 at 15:11, Arthur She arthur.she@linaro.org wrote:
Hi Steve, Since 4k hdmi dongles had been deployed to staging HiKey 01, 03, 04 and staging db410c-01 (CTT-288). I'd like to run some tests with these devices to verify the hardware.
The only way that I can think of is to submit a bunch of test jobs with
tag
'4k-hdmi-dongle'.
That *is* the documented way to do this - the device tag was created & applied solely for this purpose.
Do you have any better ideas?
Why would using the device tag be a problem?
There is no problem at all. The device tag is good and I know my case is not usual. I just want to know if there is a way that can make sure every device would be tested. Think about this case, if there are already many test jobs with different complexity in queue. If I submit a bunch of test jobs, the situation might be some of devices might run the test job multiple times and some of them might not even get one. Anyway, my problem solved. I am lucky enough, I submitted 3 test jobs and every hikey with 4k hdmi dongle got one.
The normal point of LAVA is to be testing your *software* across a range of devices, not necessarily to test it on all the devices of a particular type. The devices are meant to be as interchangeable as possible - why would you care if (say) panda01 sees less testing than panda02?
Cheers,
Hi Steve, Totally understand. My case is that we have several dummy HDMI dongles deployed to hikey 01, 02, 04 in staging LAVA. In order to verify/check if the HDMI dongles work, I have to make sure these hikey run the test job at least once. This is not a normal use case as I mentioned and I totally agree with you regarding software testing.
Thanks, Arthur
2017-08-15 11:28 GMT-07:00 Steve McIntyre steve.mcintyre@linaro.org:
Hey Arthur,
On Tue, Aug 15, 2017 at 10:43:12AM -0700, Arthur She wrote:
2017-08-15 1:32 GMT-07:00 Neil Williams neil.williams@linaro.org:
On 10 August 2017 at 15:11, Arthur She arthur.she@linaro.org wrote:
Hi Steve, Since 4k hdmi dongles had been deployed to staging HiKey 01, 03, 04
and
staging db410c-01 (CTT-288). I'd like to run some tests with these devices to verify the
hardware.
The only way that I can think of is to submit a bunch of test jobs
with
tag
'4k-hdmi-dongle'.
That *is* the documented way to do this - the device tag was created & applied solely for this purpose.
Do you have any better ideas?
Why would using the device tag be a problem?
There is no problem at all. The device tag is good and I know my case is not usual. I just want to know if there is a way that can make sure every device
would be
tested. Think about this case, if there are already many test jobs with different complexity in queue. If I submit a bunch of test jobs, the situation might be some of devices
might
run the test job multiple times and some of them might not even get one. Anyway, my problem solved. I am lucky enough, I submitted 3 test jobs and
every
hikey with 4k hdmi dongle got one.
The normal point of LAVA is to be testing your *software* across a range of devices, not necessarily to test it on all the devices of a particular type. The devices are meant to be as interchangeable as possible - why would you care if (say) panda01 sees less testing than panda02?
Cheers,
Steve McIntyre steve.mcintyre@linaro.org http://www.linaro.org/ Linaro.org | Open source software for ARM SoCs
On Tue, Aug 15, 2017 at 01:07:16PM -0700, Arthur She wrote:
Hi Steve, Totally understand. My case is that we have several dummy HDMI dongles deployed to hikey 01, 02, 04 in staging LAVA. In order to verify/check if the HDMI dongles work, I have to make sure these hikey run the test job at least once. This is not a normal use case as I mentioned and I totally agree with you regarding software testing.
Cool. :-)
Now I understand what you're trying to do - thanks for explaining some more!
Cheers,
On 15 August 2017 at 23:26, Steve McIntyre steve.mcintyre@linaro.org wrote:
On Tue, Aug 15, 2017 at 01:07:16PM -0700, Arthur She wrote:
Hi Steve, Totally understand. My case is that we have several dummy HDMI dongles deployed to hikey 01, 02, 04 in staging LAVA. In order to verify/check if the HDMI dongles work, I have to make sure these hikey run the test job at least once.
This is an admin task, albeit you're doing the work on behalf of the admins. There are two ways to do this. Either use the admin tools to take devices offline temporarily so that there is a limited number of devices with the appropriate device tag of that device type or submit enough test jobs with the required device tag so that all devices run a test job.
HiKey devices always take a nominal amount of time to setup the LXC and do a simple boot test, so if there are 4 HiKey devices with suitable device tags, it's only a case of submitting 4 test jobs within the time that it takes one HiKey to complete one test job. LAVA scheduling will take care of running as many simultaneous test jobs as there are devices available.
If there is a possibility that the dongle might work most of the time but not all the time, then you will need to submit and monitor enough jobs that each device runs enough test jobs.
Make sure that all subsequent test jobs using the dongles do a minimal smoke test that the dongle works and include that in the results by explicitly calling lava-test-case dongle-check --result pass (or --result fail if your test has detected a failed dongle, just before the test shell exits).
This is not a normal use case as I mentioned and I totally agree with you regarding software testing.
Cool. :-)
Now I understand what you're trying to do - thanks for explaining some more!
Cheers,
Steve McIntyre steve.mcintyre@linaro.org http://www.linaro.org/ Linaro.org | Open source software for ARM SoCs
Hi Neil, Thanks for your advise. Since the HDMI dongle is just a simple monitor emulator, run the test job one time should be enough. Thanks anyway.
Arthur
2017-08-16 0:55 GMT-07:00 Neil Williams neil.williams@linaro.org:
On 15 August 2017 at 23:26, Steve McIntyre steve.mcintyre@linaro.org wrote:
On Tue, Aug 15, 2017 at 01:07:16PM -0700, Arthur She wrote:
Hi Steve, Totally understand. My case is that we have several dummy HDMI dongles deployed to hikey 01,
02, 04
in staging LAVA. In order to verify/check if the HDMI dongles work, I have to make sure
these
hikey run the test job at least once.
This is an admin task, albeit you're doing the work on behalf of the admins. There are two ways to do this. Either use the admin tools to take devices offline temporarily so that there is a limited number of devices with the appropriate device tag of that device type or submit enough test jobs with the required device tag so that all devices run a test job.
HiKey devices always take a nominal amount of time to setup the LXC and do a simple boot test, so if there are 4 HiKey devices with suitable device tags, it's only a case of submitting 4 test jobs within the time that it takes one HiKey to complete one test job. LAVA scheduling will take care of running as many simultaneous test jobs as there are devices available.
If there is a possibility that the dongle might work most of the time but not all the time, then you will need to submit and monitor enough jobs that each device runs enough test jobs.
Make sure that all subsequent test jobs using the dongles do a minimal smoke test that the dongle works and include that in the results by explicitly calling lava-test-case dongle-check --result pass (or --result fail if your test has detected a failed dongle, just before the test shell exits).
This is not a normal use case as I mentioned and I totally agree with you regarding software testing.
Cool. :-)
Now I understand what you're trying to do - thanks for explaining some more!
Cheers,
Steve McIntyre steve.mcintyre@linaro.org http://www.linaro.org/ Linaro.org | Open source software for ARM SoCs
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
lava-users@lists.lavasoftware.org
-
Arthur She -
Neil Williams -
Steve McIntyre