-
Notifications
You must be signed in to change notification settings - Fork 2k
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
murdock: support emulated boards #17434
Conversation
97b43b4
to
13ab54d
Compare
7b6e339
to
c4bba0e
Compare
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. |
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.
This PR does what it claims to do. (add emulation run test to murdock)
code reads good
and (RUN_TESTS
and native
are still working)
Thanks! |
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.
microbit
is 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)