[2.7-branch] ci: backports failing on clang workflow

[cfriedt]

Describe the bug
At some point there was a change that broke the clang workflow for 2.7-branch. It has not been a high priority. However, there are backports that cannot be merged until CI is green.

From what I can tell, the clang workflow simply times-out whenever it is run.

Even if the workflow is disabled in a PR, CI still tries to run the workflow on the main branch, which has been broken for some time.

Please also mention any information which could help others to understand
the problem you're facing:

• What target platform are you using? CI
• What have you tried to diagnose or workaround this issue? Looked at all of the PRs failing.
• Is this a regression? Yes, but it was not a code commit that caused it. Something changed with the platform where the clang workflow runs

To Reproduce
Observe failing jobs in #80615 #74140 #74122 #82392

Expected behavior
CI should be green for the above backport PRs.

Impact
We shouldn't have CI failing. It's "kind of a big deal", but since LTSv2 is approaching EOL, it is not as high a priority.

We should fix it before cutting the final LTSv2 release.

Logs and console output
See failing jobs in #80615 #74140 #74122 #82392

Environment (please complete the following information):

• OS: Linux
• Toolchain: Zephyr SDK
• Commit SHA: 6477a75

Additional context

[de-nordic]

@cfriedt Thanks for raising the issue.

[cfriedt]

@stephanosio or @nashif - can you take a look? I haven't been able to fix it in the bit of time that I've had to look at it. The workflow cannot be disabled with a PR. It seems to be attempting to use the wrong runner (zephyr-runner-linux-x64-4xlarge instead of zephyr-runner-v2-linux-x64-4xlarge) and just times-out after a long time (days?).

E.g.
https://github.com/zephyrproject-rtos/zephyr/actions/runs/12132837653/job/33827367376?pr=82459

For those who have administrative privileges, it should be possible to disable workflows via the UI.

https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/disabling-and-enabling-a-workflow

Alternatively, force-push to v2.7-branch with a commit that uses the correct runner.

[nashif]

looks like we have old runner names in there, i.e.

zephyr-runner-linux-x64-4xlarge instead of zephyr-runner-v2-linux-x64-4xlarge

[nashif]

should be fixed now

[cfriedt]

This is still affecting the following two PRs after a rebase:

#74122
#82392

[nashif]

This is still affecting the following two PRs after a rebase:

#74122 #82392

both seem to be passing?

[cfriedt]

This is still affecting the following two PRs after a rebase:

#74122 #82392

both seem to be passing?

My bad - I spoke too soon. Thought they would time out because it took a long time to get picked up.

Sorry