In the kernel CI plan, OpenCV tests are executed differently compared to meta‑qcom CI, which is leading to incorrect or inconsistent test behavior.
This invocation does not use any CLI parameters and does not reference a test‑specific YAML.
In contrast, meta‑qcom CI correctly triggers the OpenCV test via its YAML:
Test definition:
https://github.com/qualcomm-linux/qcom-linux-testkit/blob/main/Runner/suites/Multimedia/OpenCV/OpenCV.yaml
Because the kernel CI plan is not invoking a test YAML, run.sh ends up running all subtests by default, which does not match the intended behavior in meta‑qcom CI and has already caused failures and ad‑hoc disables.
In the kernel CI plan, OpenCV tests are executed differently compared to meta‑qcom CI, which is leading to incorrect or inconsistent test behavior.
This invocation does not use any CLI parameters and does not reference a test‑specific YAML.
In contrast, meta‑qcom CI correctly triggers the OpenCV test via its YAML:
Test definition:
https://github.com/qualcomm-linux/qcom-linux-testkit/blob/main/Runner/suites/Multimedia/OpenCV/OpenCV.yamlBecause the kernel CI plan is not invoking a test YAML, run.sh ends up running all subtests by default, which does not match the intended behavior in meta‑qcom CI and has already caused failures and ad‑hoc disables.