cyclic test measurements have incorrect units

[Mike Holmes]

http://validation.linaro.org/dashboard/streams/public/team/linaro/ci-linux-lng/bundles/5e7be6675b47f204e7fc750b6058957669262919/59f98e41-1afc-4285-a17d-20380ec56d2e/

As can be see the Average latency test indicates that the average latency should be less than 20ns to pass and yet the test reports it took 16 usecs, yet it still records a passing state.

The pass criteria are likely system dependent and should be specified in the LAVA filters/reports rather than in the test cases its self.

Max latency bound (<15ms) 2958.0000000000 usecs
Avg latency bound (<20ns) 16.0000000000 usecs
Min latency bound (<10ns) 6.0000000000 usecs

[Vincent Hsu (vincent-hsu)]

https://git.linaro.org/gitweb?p=qa/test-definitions.git;a=blob;f=openembedded/scripts/cyclictest.py;h=aac8feb3191869e31d4747121add145e57ce2309;hb=HEAD#l54
it just caused by giving wrong units to test_case_id, but if it can be specified in the LAVA filters/reports will be better.

[Mike Holmes (mike-holmes)]

Lava filters depend on https://cards.linaro.org/browse/CARD-947

[Mike Holmes (mike-holmes)]

https://staging.review.linaro.org/#/c/451/

[Mike Holmes (mike-holmes)]

https://staging.review.linaro.org/#/c/451/ has been merged.