config: chromeos: Add ChromiumOS tree and Clang kbuild jobs

[laura-nao]

Add the ChromiumOS kernel tree (branches 5.4 to 6.12) and define new Clang kbuild jobs for both ARM64 and x86_64 Chromebooks.

[laura-nao]

Please remove the staging-skip label if the changes look good enough for testing, I believe it requires a manual trigger for staging anyway.

[10ne1]

LGTM, I assume you tested the chromeos branch with Clang 17 :)

[a-wai]

LGTM, it could be a bit more concise but there's nothing wrong with the current implementation.

[a-wai]

Suggested change

	tree:
	- chromiumos
	<<: *kbuild-clang-17-arm64-chromeos-rules

[laura-nao]

LGTM, it could be a bit more concise but there's nothing wrong with the current implementation.

Thanks for the feedback - I'll apply the fixes as suggested.

[laura-nao]

LGTM, I assume you tested the chromeos branch with Clang 17 :)

I ran just one manual LAVA job with a chromeos-6.12 build w/ Clang 17 (build was successful and boots) - see https://lava.collabora.dev/scheduler/job/17616230 for reference

I'll wait for the staging results to confirm if the other branches built successfully.

[laura-nao]

@nuclearcat is there some way to manually trigger all related builds on staging once? should I process that myself with kci-dev?

[laura-nao]

Refined branch filtering on the GCC builds as follows:

• MTK platforms: all except chromeos-5.4 and chromeos-6.6
• Qcom platforms: only chromeos-6.6
• AMD platforms: all except chromeos-5.15, chromeos-6.1, chromeos-6.6

Added also missing entries in scheduler file. Will check results on staging again and report back.

[laura-nao]

I checked the results on staging and can confirm the configuration looks correct. There were some build failures reported (e.g. https://staging.kernelci.org:9000/viewer?node_id=67ab73cd80912107775e4b6d), but they look like actual failures that can be investigated/fixed later.

There were also some incomplete jobs (e.g.: https://staging.kernelci.org:9000/viewer?node_id=67ab73c980912107775e4b4f), reporting the Node timed-out error. @nuclearcat can you help me check what happened there? I'm not sure if these errors are transitory issues with the infra or if they indicate that changes are required in this PR.
Other instances of timeouts:

• https://staging.kernelci.org:9000/viewer?node_id=67ab749880912107775e503b
• https://staging.kernelci.org:9000/viewer?node_id=67ab749580912107775e5034

[nuclearcat]

They are likely infrastructure issues, as staging restart often. Just retry one more time, but if it repeats on same jobs - i will investigate it step by step.

[nuclearcat]

I think we will merge and investigate if any issues happen