Repository navigation
bench: build the ESP32-S3 suite against the registry runtime - #45
Merged
Merged
Conversation
The firmware requires raws-labs/tigris-runtime at the suite's pinned release from the ESP Component Registry, as an application would; captures record the resolved component and its hash.
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.
The ESP32-S3 firmware now requires raws-labs/tigris-runtime from the ESP Component Registry at exactly the suite's pinned release, as an application would, instead of compiling a source checkout. The pin check holds the requirement and dependencies.lock to the pin, and captures record the resolved component and its hash. Rerun on 0.11.0: all gates pass and every latency matches the tag-checkout build.