-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[Silabs] Update Silicon Labs container #27531
[Silabs] Update Silicon Labs container #27531
Conversation
PR #27531: Size comparison from 3c8b8cf to 25c285e Increases (3 builds for bl602, bl702, nrfconnect)
Decreases (3 builds for bl602, bl702, cc32xx)
Full report (14 builds for bl602, bl702, bl702l, cc32xx, linux, mbed, nrfconnect, qpg)
|
25c285e
to
1d8af94
Compare
PR #27531: Size comparison from 25a9150 to 1d8af94 Increases (14 builds for bl602, bl702, cc32xx, esp32, nrfconnect, psoc6, telink)
Decreases (5 builds for nrfconnect, telink)
Full report (58 builds for bl602, bl702, bl702l, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
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.
In this particular case, please describe WHY the changes are needed, not just the changes themselves.
In particular, I wonder if the vscode image will need updating (and if so, how we would merge openjdk requirements between what android/java images want and openjdk items installed for efr32.
1d8af94
to
6c02878
Compare
PR #27531: Size comparison from a7edf3d to 6c02878 Increases (12 builds for bl702l, esp32, psoc6, telink)
Decreases (10 builds for bl602, bl702, cc32xx, esp32, psoc6, telink)
Full report (58 builds for bl602, bl702, bl702l, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
The Vscode image won't need updating in that case since it doesn't use slc-cli yet. This is still and ongoing effort, but on completion we should be able to remove a complete submodule from our sdk and at that point the vscode image would indeed need an update. |
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.
Adding checkmark based on separate chat to understand the issue.
Apparently the problem is that slc_cli_linux.zip
is a moving target, so docker images are inconsistent.
This change makes it so that docker build does not fail, however slc_cli as it currently exists cannot be relied upon to not change.
We only validate a sanity check for EFR32 for now, however long term expectation is that we fix slc_cli somehow (maybe submodule) and at that point we figure out the stable dependencies to put in efr32 and vscode to make it work.
Until then, developers are not expected to validate/run the slc-cli tools (which seem to be meant for a IDE integration mostly)
# RUN slc configuration --sdk="$GSDK_ROOT" && \ | ||
# slc signature trust --sdk "$GSDK_ROOT" | ||
|
||
# Install Python Packages |
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.
Based on logs now I see that the above command on line 29 will fail since requirements.txt seems gone from the zip file.
|
||
# SLC required Python Packages |
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.
these are not required by SLC, my guess is these are codegen.py requirements by the looks of it (happen to be familiar with that tool, these are exactly its dependencies).
As the title described.
Add Sphinx, and Java 17 since slc-cli (Silicon Labs specific platform generation tools) required its.
SLC CLI doesn't have the option to fetch a specific version. This is why we removed the calls from the Dockerfile. These steps, which are really quick to execute, will be made directly inside the EFR32 CI step to prevent DOcker container breakage should the SLC CLI version changes. This is far from ideal but it's the best way to do dommage control IMO.