Repository navigation
bench: rerun the ESP32-S3 suite on runtime 0.10.2 with per-suite pins - #43
Merged
Merged
Conversation
A change that can only move one target's numbers now reruns only that suite. The ESP32-S3 summary records its producing compiler and runtime revisions so its pins can be checked.
The summary's producing revisions are derived from the captures, so the tracked summary stays a byte-identical reconstruction of them.
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.
Reruns the ESP32-S3 suite on runtime 0.10.2, which no longer sleeps between stages on ESP-IDF, and pins each suite to the core that produced its own results.
core-versions.json(format 2) pins compiler and runtime per suite.check_core_versions.pychecks each suite's pins against that suite's summary and takes--suitefor the checkout check, so a change that can only move one target's numbers reruns only that suite. The Cortex-M suite keeps its pins and results.BENCH_PROVENANCE:line naming the compiler and runtime it was built from. The collector derives the summary's producing revisions from those lines, so the summary stays a byte-identical reconstruction of its captures.ESP32-S3, all result and accuracy gates pass: