tests: Run on native32 as well #261
Draft
Conversation
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
mguetschow
reviewed
Jun 4, 2025
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
mguetschow
reviewed
Jun 4, 2025
| env: | ||
| RIOT_BRANCH: '2025.01-branch' | ||
| VERSION_TAG: '2025.04' | ||
| RIOT_BRANCH: '2025.04-branch' |
There was a problem hiding this comment.
This won't work, see #256
There was a problem hiding this comment.
chrysn
force-pushed
the
test-native32-separately
branch
from
20ec8ee to
107932b
Compare
This was referenced Jun 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Trouble with 21531 indicates that running tests on native is insufficient to catch native32 trouble; this should catch that kind of issue earlier.
Created as a draft PR, because if it succeeds in this stage with only the added testing, it's not doing the right thing yet -- 21531 shows that something about the current container doesn't work on murdock, and this test is supposed to show this early. (I.e., this PR should also get some kind of fix.).