Open hristobojilov opened 4 months ago
@hristobojilov Could you log more information about value
and self._min_value
right before that check? Which one, in your case, is the string and which one is the int?
Hello, @bzbarsky-apple I've just modified /home/myuser/dev/connectedhomeip/scripts/py_matter_yamltests/matter_yamltests/constraints.py script as follows:
def check_response(self, value, value_type_name) -> bool:
print("check_response -> value is:", value, ", self._min_value is:", self._min_value)
return value >= self._min_value
The output from the print which I added is:
check_response -> value is: 40 , self._min_value is: CurrentMinMeasured+1
i.e. the int is the value 40 and the str object is CurrentMinMeasured+1.
It seems to me that CurrentMinMeasured+1 from the yaml file Test_TC_TMP_2_1.yaml is treated as string rather than as an expression to evaluate.
Hmm. That test was/is running in CI on the 1.3 branch, though. And I am pretty sure that variable substitution stuff has been around for a while.
Does changing that YAML to say CurrentMinMeasured + 1
help things for you?
After adding spaces to CurrentMinMeasured+1
now the test passes.
OK. Well, that test file seems to be replaced by a Python test on tip, but adding those spaces should help on branch....
Test issue(s)
I'm using branch v1.3-branch for matter sdk and I successfully built chip-tool and added it to $PATH. I'm trying to run Test_TC_TMP_2_1.yaml test suite against emulated matter device using this command on Ubuntu 22.04:
myuser@Matter:~/dev/connectedhomeip$ ./scripts/tests/yaml/runner.py --PICS /home/myuser/ci-pics-values --endpoint 9 Test_TC_TMP_2_1 chiptool
It seems to me that this test cannot be parsed successfully however and I'm getting this error every time:The problem seems to be caused by Test_TC_TMP_2_1.yaml:53:
minValue: CurrentMinMeasured+1
After changing it back to:minValue: CurrentMinMeasured
my problem disappears.Platform
android, other
Anything else?
No response