murdock: support emulated boards#17434
Merged
kaspar030 merged 2 commits intoRIOT-OS:masterfrom Apr 6, 2022
Merged
Conversation
97b43b4 to
13ab54d
Compare
47 tasks
7b6e339 to
c4bba0e
Compare
Contributor
Contributor
Author
|
Yup! Unfortunately our tests don't print the stack output in some (most?) cases, but that's also the case for "real" boards, so not related to this PR. |
kfessel
approved these changes
Apr 6, 2022
Contributor
Author
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contribution description
This PR adds support for emulated boards to .murdock.
Emulated boards need to be whitelisted (by adding them to .murdock's
EMULATED_BOARDS_AVAILABLE).Tests will be run for them on the build workers, similar to native.
microbitis added as first candidate.This requires and is waiting for RIOT-OS/riotdocker#168.(merged)I'm expecting some tests to fail on the emulated microbit, as the emulation is not complete.I'll add those to the CI blacklist, probably guarded by "EMULATE=1".
All failing tests have been CI test blacklisted. I've created a tracking issue: #17894
Testing procedure
CI should be fine.
Issues/PRs references
This is stumbling over #17555.(resolved)