LAVA regexp does not handle "none" in measurements
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LAVA Project |
Confirmed
|
Medium
|
Tyler Baker |
Bug Description
The following data is a snippet from 10s of results that have multiple measurement data and an overall result for the test, requiring the mixing of LAVA results which have measurements and some without measurements all in the same run.
For eample the test produces
sched_
sched_
Externally to lava this regexp works
^(?
Using non matching (:?..) parens and the 0 or 1 '?'
Giving:-
units us
measurement 12.1115
result skip
test_case_id sched_latency_
units None
measurement None
result FAIL
test_case_id sched_latency_test
LAVA gives results like the following, and it looks like it sees the "None" for the measurement and freaks out that it is not a number :)
Traceback (most recent call last):
File "/srv/lava/
testruns.
File "/srv/lava/
'
File "/srv/lava/
res[
File "/usr/lib/
raise TypeError("Cannot convert %r to Decimal" % value)
TypeError: Cannot convert None to Decimal
It would be nice for the "None" case where presumably the none is becasue there was no match for measurement, if it did not try to convert it to a decimal.
summary: |
- LAVA regexp does not handle "none" in masurements + LAVA regexp does not handle "none" in measurements |
Changed in lava-project: | |
importance: | Undecided → Medium |
assignee: | nobody → Tyler Baker (tyler-baker) |
status: | New → Confirmed |
agreed, LAVA should be able to handle a None value properly when there is no match