config: chromeos: add codec-related Tast tests

[a-wai]

Those were left aside for the initial implementation, we can bring them back now we're confident Tast tests generally run as expected on the new system.

Based on kernelci/kernelci-core#2302

[JenySadadia]

Adding staging-skip due to below errors on staging:

kernelci-pipeline-trigger | Traceback (most recent call last):
kernelci-pipeline-trigger |   File "/home/kernelci/./pipeline/trigger.py", line 163, in <module>
kernelci-pipeline-trigger |     configs = kernelci.config.load(yaml_configs)
kernelci-pipeline-trigger |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger |   File "/usr/local/lib/python3.11/site-packages/kernelci/config/__init__.py", line 191, in load
kernelci-pipeline-trigger |     data = load_yaml(config_paths)
kernelci-pipeline-trigger |            ^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger |   File "/usr/local/lib/python3.11/site-packages/kernelci/config/__init__.py", line 149, in load_yaml
kernelci-pipeline-trigger |     data = load_single_yaml(path)
kernelci-pipeline-trigger |            ^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger |   File "/usr/local/lib/python3.11/site-packages/kernelci/config/__init__.py", line 86, in load_single_yaml
kernelci-pipeline-trigger |     for _, data in iterate_yaml_files(config_path):
kernelci-pipeline-trigger |   File "/usr/local/lib/python3.11/site-packages/kernelci/config/__init__.py", line 30, in iterate_yaml_files
kernelci-pipeline-trigger |     data = yaml.safe_load(yaml_file)
kernelci-pipeline-trigger |            ^^^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger |   File "/usr/local/lib/python3.11/site-packages/yaml/__init__.py", line 125, in safe_load
kernelci-pipeline-trigger |     return load(stream, SafeLoader)
kernelci-pipeline-trigger |            ^^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger |   File "/usr/local/lib/python3.11/site-packages/yaml/__init__.py", line 81, in load
kernelci-pipeline-trigger |     return loader.get_single_data()
kernelci-pipeline-trigger |            ^^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger |   File "/usr/local/lib/python3.11/site-packages/yaml/constructor.py", line 49, in get_single_data
kernelci-pipeline-trigger |     node = self.get_single_node()
kernelci-pipeline-trigger |            ^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger |   File "/usr/local/lib/python3.11/site-packages/yaml/composer.py", line 36, in get_single_node
kernelci-pipeline-trigger |     document = self.compose_document()
kernelci-pipeline-trigger |                ^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger |   File "/usr/local/lib/python3.11/site-packages/yaml/composer.py", line 55, in compose_document
kernelci-pipeline-trigger |     node = self.compose_node(None, None)
kernelci-pipeline-trigger |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger |   File "/usr/local/lib/python3.11/site-packages/yaml/composer.py", line 84, in compose_node
kernelci-pipeline-trigger |     node = self.compose_mapping_node(anchor)
kernelci-pipeline-trigger |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger |   File "/usr/local/lib/python3.11/site-packages/yaml/composer.py", line 133, in compose_mapping_node
kernelci-pipeline-trigger |     item_value = self.compose_node(node, item_key)
kernelci-pipeline-trigger |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger |   File "/usr/local/lib/python3.11/site-packages/yaml/composer.py", line 84, in compose_node
kernelci-pipeline-trigger |     node = self.compose_mapping_node(anchor)
kernelci-pipeline-trigger |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger |   File "/usr/local/lib/python3.11/site-packages/yaml/composer.py", line 133, in compose_mapping_node
kernelci-pipeline-trigger |     item_value = self.compose_node(node, item_key)
kernelci-pipeline-trigger |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger |   File "/usr/local/lib/python3.11/site-packages/yaml/composer.py", line 68, in compose_node
kernelci-pipeline-trigger |     raise ComposerError(None, None, "found undefined alias %r"
kernelci-pipeline-trigger | yaml.composer.ComposerError: found undefined alias 'tast-decoder-v4l2-sl-av1-job'
kernelci-pipeline-trigger |   in "config/jobs-chromeos.yaml", line 417, column 44

[a-wai]

Adding staging-skip due to below errors on staging:

Fixed, sorry about that!

[a-wai]

@laura-nao Thanks for the review! One thing I was wondering: could we make vp9-group{1,2,3,4} a single job? It seems those should always run on the same platforms, unless you anticipate changes to happen there?

We might also group vp9-level5 and vp9-svc a single job named vp9-extra for instance, although I don't know if this would really make sense.

[laura-nao]

@laura-nao Thanks for the review! One thing I was wondering: could we make vp9-group{1,2,3,4} a single job? It seems those should always run on the same platforms, unless you anticipate changes to happen there?

We might also group vp9-level5 and vp9-svc a single job named vp9-extra for instance, although I don't know if this would really make sense.

@a-wai when I first added these tests in the legacy system, I noticed that a job running all vp9 tests would exceed 10 minutes so I opted for splitting them into groups. I'm not against combining them into a single suite (especially if it makes more sense from a resource usage pov), it will just take more time to execute and I'm not sure if the best practice of avoiding jobs >10min still stands for the new system or not.

[a-wai]

@laura-nao well we already have multiple Tast jobs >10mins, so I'd say this "rule" at least has a few exceptions, Tast tests being one of them. I'll proceed with grouping tests as I suggested then, if it doesn't work we can always revert that later.

[nuclearcat]

Tests being run, might be failing now, but this might be next step fixing minor details
https://staging.kernelci.org:9000/viewer?search=parent%3D65eac74577d9d88b36edbb6b