-
Notifications
You must be signed in to change notification settings - Fork 2.1k
build-system: pin new docker image #21531
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
build-system: pin new docker image #21531
Conversation
This ensures that `make BUILD_IN_DOCKER=1` will use the same container that was used in the CI (Murdock).
Trouble with [21531] indicates that running tests on native is insufficient to catch native32 trouble; this should catch that kind of issue earlier. [21531]: RIOT-OS/RIOT#21531
Trouble with [21531] indicates that running tests on native is insufficient to catch native32 trouble; this should catch that kind of issue earlier. [21531]: RIOT-OS/RIOT#21531
|
That's weird -- admittedly, the riotbuild tests only run on native and not separately on native32 and native64, but I can't remember ever having had differentiated issues. Checking that is now blocked 3 issues deep: this one would be addressed by RIOT-OS/riotdocker#261 but that's stuck as it needs RIOT-OS/riotdocker#256 but that needs some cleanup after #21359 |
|
@maribu a way to break the CI-stuck loop would be to blacklist |
Until the bug is fixed
77bd10d to
0a21b4d
Compare
|
Backport provided in #21541 |
Contribution description
This ensures that
make BUILD_IN_DOCKER=1will use the same container that was used in the CI (Murdock).Testing procedure
Green CI
Issues/PRs references
None