-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rimage: update submodule to 542924d70c17, back in sync with west.yml (fixes -dirty) #6398
Conversation
Fixes commit a3b3c52 ("west: update to newer rimage baseline") 542924d config: tgl-h-cavs: add probe module 5b076f1 config: tgl-cavs: add probe module 6b4848e mtl: Add UPDWMIX module to the manifest d50aefc manifest max size for loadable modules d94cfc9 mtl: add MicSel support 5504179 Add lib_code module type. 12bb327 toml: add tgl-h config file for IPC4 452847d mtl: Add SRC module to the manifest Signed-off-by: Marc Herbert <[email protected]>
Just for the record the
|
|
All the compilation failures found by https://github.com/thesofproject/sof/actions/runs/3229592866/ happen ONLY with the bleeding edge zephyr main branch, the manifest revision of Zephyr always builds fine. |
The changes in this PR looks good but I don't get '-dirty' problem. '-dirty' post fix is attached when local change is present, isn't it. Can you educate more? Why -dirty problem was there before and how that is fixed by this PR? |
Try this:
|
https://sof-ci.01.org/sofpr/PR6398/build1818/devicetest/?model=TGLU_UP_HDA_ZEPHYR&testcase=verify-kernel-boot-log is lacking a monitor (https://github.com/intel-innersource/drivers.audio.ci.sof-framework/issues/294), everything else is green. |
https://sof-ci.01.org/sof-pr-viewer/#/build/PR6398/build10541812 failed with
@wszypelt port 84300 is deprecated, please switch to 18764 https://sof-ci.01.org/sofpr/PR6398/build1818/devicetest/?model=TGLU_UP_HDA_ZEPHYR&testcase=verify-kernel-boot-log is missing a monitor - harmless |
@marc-hb |
Trying avoid out-of-sync situations like commit a3b3c52 ("west: update to newer rimage baseline"). Also explain why sof cannot be cloned as "sof2" Signed-off-by: Marc Herbert <[email protected]>
94fd483
to
68ada05
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving but see comment inline.
# describe` notice and a "-dirty" suffix appears in the SOF version. | ||
# It is generally very bad practice to git push without looking | ||
# at "git status"; even without submodules. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given we will need frequent updates to rimage (like #6385 today), the above seems just way too complicated. Can we use a different directory for either the submodule (renaming it) or the west module? This probably needs to be done in steps to remove the hardcodes for rimage path, before the switch, but I don't see we can survive with this duplicated rimage copies setup in the long term.
Not blocking the PR because of this, as long as we use the same directory name, this is needed yes or yes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the best would be to move rimage one level-up in west.yml and leave the rimage submodule in place. west would then stop fooling git submodules. This would help de-hardcoding the sof
name of the sof clone too.
BTW west
is suspiciously quiet about nesting git repos. It does not explicitly forbid it but it never shows any nested git repo in any example anywhere in the documentation.
HOWEVER, moving rimage in west.yml would require large, disruptive and backwards-incompatible changes in the build system and in CI, which is why it was not done yet. I mean much more complicated and much more time-consuming changes than keeping the submodule in sync. Good request to add the backlog though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given we will need frequent updates to rimage (like #6385 today),
BTW rimage updates were not really frequent in the past. They are more frequent now because MTL is brand new but I would expect this to ease off soon. As long as the firmware boots who cares about rimage?
Common suspend/resume failure in https://sof-ci.01.org/sofpr/PR6398/build1856/devicetest/?model=TGLU_UP_HDA_ZEPHYR&testcase=check-suspend-resume-5 I think this warning was just fixed
Everything else green, good to go. |
Fourth failure in "Internal Intel CI System/merge/build", IPC3 smoke test. FYI @wszypelt |
Fixes commit a3b3c52 ("west: update to newer rimage baseline")
See commit messages and new warning in west.yml