'list' object has no attribute 'items'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LAVA Dispatcher |
Confirmed
|
Medium
|
Tyler Baker |
Bug Description
Hi,I came accross this bug when I created a Multinode Job. It seem something wrong when I use default parameters.
:
ErrorMessage: 'list' object has no attribute 'items'
Lava failed at action lava_test_shell with error:'list' object has no attribute 'items'
Traceback (most recent call last):
File "/srv/lava/
action.
File "/srv/lava/
testdef_repos, skip_install)
File "/srv/lava/
testdef.
File "/srv/lava/
URLTestDefini
File "/srv/lava/
self.
File "/srv/lava/
self.
File "/srv/lava/
for def_param_name, def_param_value in self.testdef[
AttributeError: 'list' object has no attribute 'items'
The link is:
https:/
https:/
affects: | lava-android-benchmark-views → lava-dispatcher |
Changed in lava-dispatcher: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
assignee: | nobody → Tyler Baker (tyler-baker) |
Hi Weilong,
You yaml does not take any parameters, yet you pass them in the JSON:
https:/ /validation. linaro. org/scheduler/ job/129800/ multinode_ definition
https:/ /git.linaro. org/people/ weilong. chen/lgp1. git/blob/ HEAD:/openembed ded/odp- generator- client. yaml
https:/ /git.linaro. org/people/ weilong. chen/lgp1. git/blob/ HEAD:/openembed ded/odp- generator- server. yaml
Here is an example of a YAML which defines parameters:
https:/ /git.linaro. org/qa/ test-definition s.git/blob/ HEAD:/openembed ded/netperf- client- multinode. yaml#l22
I agree though, that LAVA should produce a better error in this case. This will be fixed.