CI: update run-all-steps baseline data#125
Merged
Merged
Conversation
sporksmith
force-pushed
the
update-golden-2026-06
branch
from
2a8546e to
5d1dc58
Compare
sporksmith
changed the title
robgjansen
approved these changes
Jun 29, 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.
It's been a while since this baseline has been updated. Notably it looks like
TOR_COMMIT,TGEN_COMMIT,ONIONTRACE_COMMIT, andSHADOW_COMMIThave all been bumped since the last baseline update. (See the diff of the autogenerated READMEThis is a purely mechanical; I pushed an empty commit allowing the CI to run, and then unpacked the
run_all_steps_output.zipartifact into.github/workflows/run_all_steps_output