-
Notifications
You must be signed in to change notification settings - Fork 481
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
Zephyr builds: revert to latest ci image once fix is available #1948
Comments
Workaround by downgrading to 0.26.14 proposed in PR #1949 |
Just looked into it. As indicated in zephyrproject-rtos/docker-image#205, this should (hopefully) be a temporary issue. The fix is already merged in the upstream SDK repo, so only the docker image must be updated. Your workaround in #1949 should be totally fine until the SDK container is fixed. |
Thanks for the confirmation @Frauschi. |
Keeping the issue open to revert #1949 once an updated container is available. |
I just opened a PR (#1953) to switch back to the latest container, as there is a new container resolving the issue. |
Zephyr builds in CI fail since about a week, while the liboqs changes in the builds seem unrelated to zephyr.
The timing coincides with a zephyr container update https://github.com/zephyrproject-rtos/docker-image/pkgs/container/ci/282662529?tag=main-amd64.
I haven't found the root cause of the build failure, but zephyrproject-rtos/docker-image#205 suggests there might be an issue with the SDK used in the container image and the recommendation is to downgrade to v0.26.14. Do you have any insight here @Frauschi ?
The text was updated successfully, but these errors were encountered: