Skip to content

Conversation

@marc-hb
Copy link
Collaborator

@marc-hb marc-hb commented Dec 9, 2025

Fixes commit 56649f6 ("github: workflows: disable sparse checks temporarily") which caused a syntax error

GitHub jobs can be disabled one by one but not all at once: https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#jobsjob_idif

This syntax error was found by Copilot; quoting the original PR:

The if: false statement is incorrectly placed at the file level
between jobs: and the job definition. This will cause a syntax
error. It should be placed within a specific job definition. Move this
line and the preceding comments to be indented under the job
name (e.g., after the job key on the next line

This has blocked daily tests from running for ages:

https://github.com/thesofproject/sof/actions/runs/20048113632

Invalid workflow file: .github/workflows/daily-tests.yml#L42
error parsing called workflow
".github/workflows/daily-tests.yml"
-> "./.github/workflows/sparse-zephyr.yml"
  (source branch with sha:e00764e7fbe3315c0d8e1fa87624aec4e37db7e3)
: (Line: 17, Col: 7): Unexpected value 'false'

Fixes commit 56649f6 ("github: workflows: disable sparse checks
temporarily") which caused a syntax error

GitHub jobs can be disabled one by one but not all at once:
https://docs.github.com/en/actions/reference/workflows-and-actions/
                         workflow-syntax#jobsjob_idif

This syntax error was found by Copilot; quoting:
thesofproject#10337 (comment)

> The if: false statement is incorrectly placed at the file level
> between jobs: and the job definition. This will cause a syntax
> error. It should be placed within a specific job definition. Move this
> line and the preceding comments to be indented under the job
> name (e.g., after the job key on the next line

This has blocked daily tests from running for ages:

https://github.com/thesofproject/sof/actions/runs/20048113632
```
Invalid workflow file: .github/workflows/daily-tests.yml#L42
error parsing called workflow
".github/workflows/daily-tests.yml"
-> "./.github/workflows/sparse-zephyr.yml"
  (source branch with sha:e00764e7fbe3315c0d8e1fa87624aec4e37db7e3)
: (Line: 17, Col: 7): Unexpected value 'false'
```

Signed-off-by: Marc Herbert <marc.herbert@intel.com>
@marc-hb marc-hb changed the title .github: really disable spar-se instead of breaking it [SKIP SOFCI] .github: really disable spar-se instead of breaking it Dec 10, 2025
@marc-hb
Copy link
Collaborator Author

marc-hb commented Dec 10, 2025

Syntax error is gone:

Screenshot 2025-12-09 at 16 04 54

(Added [SKIP SOFCI] but too late, sorry)

@marc-hb marc-hb marked this pull request as ready for review December 10, 2025 00:05
@marc-hb marc-hb changed the title [SKIP SOFCI] .github: really disable spar-se instead of breaking it [SKIP SOF-TEST] .github: really disable spar-se instead of breaking it Dec 10, 2025
Copy link
Collaborator

@kv2019i kv2019i left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @marc-hb , I'm not claiming I knew what I was doing and obviously nobody is looking at the github daily results. :(

@kv2019i kv2019i merged commit 2bf8638 into thesofproject:main Dec 10, 2025
36 of 43 checks passed
@marc-hb marc-hb deleted the sparse-gh-syntax branch December 10, 2025 17:19
@marc-hb
Copy link
Collaborator Author

marc-hb commented Dec 10, 2025

obviously nobody is looking at the github daily results. :(

Nobody does but they are still very useful when GitHub or something upgrades a container or similar and some obscure regression or incompatibility sneaks in. Then, Pull Requests start failing mysteriously and everyone is scratching their head - until they look at daily test results that immediately pinpoint the regression. That's the main purpose.

There's also a red/green badge on the project front page: https://github.com/thesofproject/sof

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants