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