test(live): adr-migrate restores v0 records from snapshots beside the scenario - #585
Merged
Merged
Conversation
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.
Summary
scenarios/adr-migrate/v0/, taken from main before feat(adr): agent-ways adopts adr/v1 and migrates a first sample #581 (cec7a370^1). Before this, it restored them from the merge-base with main.--depth 1clone, so they ship with the test.Why
Today's tier 2 dispatch on main (run 36330173187) failed at
setup.sh ran. Main now carries both records as v1, and the setup's guard refuses a rehearsal that would test nothing. In the release flavor, the merge-base lookup had always failed silently. It only passed because main still had the records as v0.