test(freeze): add live smoke test for freeze create/update/delete#1436
Open
Conversation
Member
Author
|
This pull request is part of a Mergify stack:
|
This was referenced May 19, 2026
Contributor
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🔴 ⛓️ Depends-On RequirementsWaiting for
This rule is failing.Requirement based on the presence of
🔴 👀 Review RequirementsWaiting for
This rule is failing.
🔴 🔎 ReviewsWaiting for
This rule is failing.
🟢 🤖 Continuous IntegrationWonderful, this rule succeeded.
🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 📕 PR descriptionWonderful, this rule succeeded.
|
jd
force-pushed
the
devs/jd/worktree-rust-port/add-live-smoke-test-freeze-create-update-delete--9a7b270e
branch
from
f77ec67 to
414a70b
Compare
Member
Author
Revision history
|
This was referenced May 19, 2026
jd
force-pushed
the
devs/jd/worktree-rust-port/add-live-smoke-test-freeze-create-update-delete--9a7b270e
branch
from
414a70b to
8106d1c
Compare
Pin `POST` + `PATCH` + `POST .../{id}/delete` against the real
Mergify API as a single round-trip. The freeze is scheduled far
in the future (2099) so the server treats it as `scheduled` (no
active-freeze delete reason needed) and the test repo's queue
isn't disturbed. The delete runs from `finally` so cleanup is
guaranteed even when an assertion in the middle fails.
Uses `live_admin_token` because scheduled-freeze endpoints sit
under the queue-management family; the CI-scoped token is
rejected with 403. Each run picks a unique `func-tests-live-
smoke-<ts>` reason so concurrent or repeated runs don't fight
over the same row.
The freeze ID is parsed out of the create command's human
output (the same `_print_freeze` block the Rust port mirrors),
so the regex pins the per-freeze output format across both ends
of the port.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Change-Id: I9a7b270e04b86ca1bf71985b92350bee29d26f80
jd
force-pushed
the
devs/jd/worktree-rust-port/port-freeze-list-native-rust--40ca436a
branch
from
078f0e6 to
fca204c
Compare
jd
force-pushed
the
devs/jd/worktree-rust-port/add-live-smoke-test-freeze-create-update-delete--9a7b270e
branch
from
8106d1c to
fa07747
Compare
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.
Pin
POST+PATCH+POST .../{id}/deleteagainst the realMergify API as a single round-trip. The freeze is scheduled far
in the future (2099) so the server treats it as
scheduled(noactive-freeze delete reason needed) and the test repo's queue
isn't disturbed. The delete runs from
finallyso cleanup isguaranteed even when an assertion in the middle fails.
Uses
live_admin_tokenbecause scheduled-freeze endpoints situnder the queue-management family; the CI-scoped token is
rejected with 403. Each run picks a unique
func-tests-live- smoke-<ts>reason so concurrent or repeated runs don't fightover the same row.
The freeze ID is parsed out of the create command's human
output (the same
_print_freezeblock the Rust port mirrors),so the regex pins the per-freeze output format across both ends
of the port.
Co-Authored-By: Claude Opus 4.7 noreply@anthropic.com
Depends-On: #1435