You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Git submodule rimage revision had not been updated during last update of the west.yml file.
Looks like regression introduced in the #7630 .
It had been changed in west manifest from ab0429f to 4ce79b1 however, during work with git rimage submodule shows changes.
To Reproduce
execute command west update
execute command git status (now rimage submodule has changes - dirty state)
execute command git submodule update --init --recursive and confirm that SHA ab0429f is checked out (bad revision).
Reproduction Rate
100%.
Expected behavior Git status does not show changes in rimage submodule.
Impact
Annoyance.
Environment
Branch name and commit hash of the 2 repositories: sof (firmware/topology) and linux (kernel driver).
Kernel: N/A
SOF: main
Name of the topology file
Topology: N/A
Name of the platform(s) on which the bug is observed.
@fredoh9 please double check whether your PR introduces this and fix if I am right.
Guys please take cautious with this. I know it's tiresome to track revision in both git and west but please do so until we migrate to west completely.
Describe the bug
Git submodule rimage revision had not been updated during last update of the west.yml file.
Looks like regression introduced in the #7630 .
It had been changed in west manifest from ab0429f to
4ce79b1 however, during work with git rimage submodule shows changes.
To Reproduce
west update
git status
(now rimage submodule has changes - dirty state)git submodule update --init --recursive
and confirm that SHA ab0429f is checked out (bad revision).Reproduction Rate
100%.
Expected behavior
Git status
does not show changes in rimage submodule.Impact
Annoyance.
Environment
Screenshots or console output
rimage bad revision.log
The text was updated successfully, but these errors were encountered: