Conversation
nyonson
force-pushed
the
no-std-tests
branch
4 times, most recently
from
e5001b3 to
7d21f0e
Compare
Checking in the lock file for the integration tests package since an update to cargo-rbmt started to use the --locked flag which breaks on any dependency version changes. This might need to be re-worked to be more maintainable, I could see it falling out of date. But will give it a shot first.
tcharding
approved these changes
Jan 11, 2026
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
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.
Testing out the new cargo-rbmt thing where it tests no-std if it detects it. Required switching to
#![no_std]since cargo-rbmt doesn't do any parsing, but this is kind of easier to read anyways?Not sure how terrible it is to have to install the ARM compiler like this.