glamsterdam-devnet-7: pin eest_ref to frozen benchmarks/amsterdam - #22
Merged
Conversation
forks/amsterdam now merges devnet-8 spec PRs, so the next refill (due after the state-actor datadir regen) would fill repricing payloads from a drifted spec. benchmarks/amsterdam is the frozen pre-devnet-8 snapshot (exact ancestor 178d9f9); pinning it matches the other subdirs, which already fill from dedicated frozen branches.
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
1 participant
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.
forks/amsterdamnow merges devnet-8 spec PRs, so the next repricing refill — due anyway once the state-actor datadirs are regenerated (see #benchmarking) — would fill thestateful/computepayloads from a drifted spec.benchmarks/amsterdamis the frozen pre-devnet-8 snapshot of the same branch (exact ancestor, tip178d9f9), so today this is a pure pin: the fill input is byte-identical untilforks/amsterdammoves further.The other subdirs already follow this convention (
bal-devnet-7→louistsai-csie-devnet-7-bench-fill-stateful-fixes,glamsterdam-devnet-6→devnets/glamsterdam/6-benchmarks).No refill is triggered by this PR itself — fills only happen on
benchmarkoor-build.yamldispatch. Companion to #21, which uses the same ref for the new full-suite test types.