Raul Marquez
Raul Marquez
Basically the test in the CI was timing out due to performing a read before the value was available due to the different response times in different network environments. The...
> Changes to tests.yaml is too large. We should only have potential changes to a line for TC_IDM_4_2.py (or no changes if execution logic is not changed) Updated tests.yaml
As per a conversation with @raju-apple and @cecille, this TC will not go in for 1.3 and is suggested to be ported to Python, it'll remain on hold.
Addressed in this PR: https://github.com/project-chip/certification-tool-frontend/pull/11
PRs addressing the issue: **Frontend**: [Updates create and repeat test run execution to match backend changes #13](https://github.com/project-chip/certification-tool-frontend/pull/13) **Backend**: [[Fix] remove TestRunConfig usage from TH Backend (#581) #6](https://github.com/project-chip/certification-tool-backend/pull/6)
Related [TC-IDM-4.3: Update and automate #308 ](https://github.com/project-chip/matter-test-scripts/issues/308)
--trace-to is part of what command? @fabiowmm, @tcarmelveilleux, can you provide instructions to reproduce?
@tcarmelveilleux From our conversation - We need a way to ensure that the executed command line for the Python tests have --trace-to json:log on it by default - The finding...
@tcarmelveilleux, from the screenshot shared by @rquidute, does that resolve the issue?
Addressed in PR https://github.com/project-chip/certification-tool-frontend/pull/23