Closed musamaanjum closed 6 days ago
@igaw FYI
This is breaking staging:
Attaching to kernelci-pipeline-trigger
kernelci-pipeline-trigger | Traceback (most recent call last):
kernelci-pipeline-trigger | File "/home/kernelci/./pipeline/trigger.py", line 179, 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 192, in load
kernelci-pipeline-trigger | return load_data(data)
kernelci-pipeline-trigger | ^^^^^^^^^^^^^^^
kernelci-pipeline-trigger | File "/usr/local/lib/python3.11/site-packages/kernelci/config/__init__.py", line 174, in load_data
kernelci-pipeline-trigger | config.update(mod.from_yaml(data, filters))
kernelci-pipeline-trigger | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger | File "/usr/local/lib/python3.11/site-packages/kernelci/legacy/config/__init__.py", line 20, in from_yaml
kernelci-pipeline-trigger | config.update(build_config.from_yaml(data, filters))
kernelci-pipeline-trigger | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger | File "/usr/local/lib/python3.11/site-packages/kernelci/legacy/config/build.py", line 462, in from_yaml
kernelci-pipeline-trigger | build_configs = {
kernelci-pipeline-trigger | ^
kernelci-pipeline-trigger | File "/usr/local/lib/python3.11/site-packages/kernelci/legacy/config/build.py", line 463, in <dictcomp>
kernelci-pipeline-trigger | name: BuildConfig.load_from_yaml(
kernelci-pipeline-trigger | ^^^^^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger | File "/usr/local/lib/python3.11/site-packages/kernelci/legacy/config/build.py", line 399, in load_from_yaml
kernelci-pipeline-trigger | variants = [
kernelci-pipeline-trigger | ^
kernelci-pipeline-trigger | File "/usr/local/lib/python3.11/site-packages/kernelci/legacy/config/build.py", line 400, in <listcomp>
kernelci-pipeline-trigger | BuildVariant.load_from_yaml(variant, name, fragments, b_envs)
kernelci-pipeline-trigger | File "/usr/local/lib/python3.11/site-packages/kernelci/legacy/config/build.py", line 315, in load_from_yaml
kernelci-pipeline-trigger | kw['architectures'] = list(
kernelci-pipeline-trigger | ^^^^^
kernelci-pipeline-trigger | File "/usr/local/lib/python3.11/site-packages/kernelci/legacy/config/build.py", line 316, in <genexpr>
kernelci-pipeline-trigger | Architecture.load_from_yaml(data or {}, name, fragments)
kernelci-pipeline-trigger | File "/usr/local/lib/python3.11/site-packages/kernelci/legacy/config/build.py", line 179, in load_from_yaml
kernelci-pipeline-trigger | kw['fragments'] = [fragments[name] for name in cf] if cf else None
kernelci-pipeline-trigger | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
kernelci-pipeline-trigger | File "/usr/local/lib/python3.11/site-packages/kernelci/legacy/config/build.py", line 179, in <listcomp>
kernelci-pipeline-trigger | kw['fragments'] = [fragments[name] for name in cf] if cf else None
kernelci-pipeline-trigger | ~~~~~~~~~^^^^^^
kernelci-pipeline-trigger | KeyError: 'arm64-chromebook'
There was fragments-related error. @JenySadadia could you review it again to see if following has help?
I've updated the format of fragments to use strings (with '
, previously it was without '
):
fragments:
- 'abc'
@JenySadadia @nuclearcat the error is still present. I'm using fragment in pipeline. Any ideas what's going wrong? The same fragment is working fine in jobs-chromeos.yaml.
Thanks @pawiecz. I've updated the PR.
Tested locally seem to be working now. Removig staging-skip tag. Feel free to add it again if it causes issues.
@pawiecz @nuclearcat I'm getting results on some branches. kbuilds.html.txt
I've not enabled stable-rt builds for i386 and riscv. But still, I can find results for these architectures. I'll check the PR.
I've looked at the PR and I've not enabled these builds on i386 and riscv. What reason do you see for this behaviour?
See the description in individual commits.