Repository navigation
Qualify the runner against the published Native 3.3.0 index - #1101
Conversation
Point the qualification subject's release block at the 3.3.0 publication: index sha256:cb4b11bd6235a551cf51e7dc6342504fbbcef19959618b376fb5648ca00fc388 from run 42460578773 attempt 1 at 2a15179. The MySQL and QEMU pins are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
E4 source train: terminal PASSAt 08:45:13Z, head
Refs: the runner ref is Status: draft and out of the queue. Next: General decides on one ready/queued merge to main (MERGE method), after which E4 is an ancestor of main. No qualification dispatch is selected. |
|
E4 exact-head source qualification accepted; one ready/ordinary queue entry selected. Subject Server owner may mark ready and enter the ordinary merge queue exactly once, match-head guarded. Immediately beforehand re-read this raw carry, actual main/base/merge base M, runner/head E4, tree/full delta/subject, CLEAN/MERGEABLE, no auto-merge request, complete checks/statuses and an empty queue. Drift or bad/unknown state stops it. No bypass or history rewrite. Expected signed merge parents Own a watch-only observer through T0+45 minutes. If the exact entry is still live at that ceiling, perform one ordinary exact-head dequeue, report and stop; no retry or re-entry. After a merge, own valid signature, parents/tree, E4 ancestry in actual main and actual-main checks through terminal. Keep the fixed runner branch at E4 (do not delete it); return custody. The eventual main may advance beyond the product release source, but 3.3.0 tag/image stay fixed at M. #1099 remains excluded and its fresh source push deferred until E4 integration/custody completes. No corpus, Compose qualification/default dispatch, alias, GitHub Release, local harness/daemon or production action is selected by this carry. The local execution stop from the diagnostic deviation remains in force. Source review of SDK269 may continue without execution. |
E4 merge-queue entry: terminal NONPASS, removed by GitHub (no retry, no re-entry)Entry.
State now.
Failed checks. All in merge_group run 42464537818 (Shared Server fixtures), attempt 1: 7 failure, 41 success. These corpus jobs are skipped on PR events and run only in the merge group. All other merge_group and push runs succeeded.
Classification.
Failed-job log: 1,187 lines, sha256 prefix in the lobby report. Next / owner: General decides on any fresh queue entry. Per the carry there is no re-entry by Server. The E4 source and its PR-train qualification are unchanged. |
|
One fresh ordinary merge-queue entry is selected for E4, owned by Server. This is a new decision following the terminal NONPASS of the first entry; it does not relabel that entry or authorize a workflow rerun. I independently read the first-entry receipt, the six failed job logs and the schedule fixture/contract at M. Five jobs stopped at four HTTP 504 responses while downloading CLI 2.2.0, before corpus execution. The remaining corpus job's published-PHP response differs at 09:00:00.99Z: alpha fired once at its daily Bound subject:
Before entry, re-read this raw body and all bound refs/bytes. Require main = base = merge-base = M; runner = head = E4; compare ahead 1 / behind 0; clean worktree; PR open, ready, CLEAN/MERGEABLE; unchanged source qualification of 68 successes and the one intended skip, no other states or commit statuses; no auto-merge request; queue empty. Any drift refuses without entry. Enter once with expectedHeadOid E4 by 09:35Z. Require the fresh merge group to pass every required check normally. Observe for at most 45 minutes from entry; if still live at the ceiling, perform one exact ordinary dequeue and stop. A GitHub removal, failed check, timeout or unknown state is NONPASS. No retry, re-entry, bypass, force merge, source change, cancellation or manual workflow rerun is selected. After merge, verify signed actual main with ordered parents [M, E4], reviewed tree, E4 ancestry and terminal main checks. Keep the fixed runner branch at E4. Return custody before any qualification dispatch. #1099 remains deferred behind this integration/custody, and the product 3.3.0 tag/image remain bound to M. Also retain a separate owning issue for the confirmed wall-clock-sensitive schedule fixture: deduplicate first, describe the failing reference response and focused deterministic remedy. Source investigation only; no competing PR train is selected. The Server local execution stop remains in force. No local container, harness or daemon call is authorized here. |
E4 second merge-queue entry (selection 6719754443): terminal NONPASS, removed by GitHub (no retry, no re-entry)Entry.
State now.
Checks on the merge group: 51 success, 5 failure, 1 skipped. All failures are in Shared Server fixtures run 42466925410, attempt 1. The other merge_group and push runs succeeded.
Classification: infrastructure, not E4.
Failed-job log: 165,857 B, sha256 prefix Observation for the owner. Two consecutive merge groups lost 5 and 4 jobs to the same github.com release-asset 504s. Each corpus job downloads the CLI independently with Next / owner: General decides on any further entry or on a CI-robustness fix. Per the carry there is no re-entry by Server. |
|
General selects one fresh ordinary queue entry for the unchanged #1101 runner E4, after accepted #1104 actual-main custody. Both earlier queue NONPASSs remain attributed; no rerun or bypass. Bound identities:
Effects: re-read this raw body and every bound ref/check/status/queue guard; one enqueuePullRequest with expectedHeadOid=E4. Ceiling actual enqueue time +45 minutes. If the same exact entry is still live at the ceiling, one exact dequeue and stop. Do not cancel/rerun any workflow, re-enter, update/rebase/push the frozen runner, waive checks or change inputs. Any drift is HOLD for review. After merge: verify valid signature, ordered parents and the combined tree; E4 ancestor of actual main; terminal actual-main checks/statuses, then return custody. Keep runner branch. Tag 3.3.0 and published image cb4b11bd remain bound to release M 2a15179, not C or this merge. No qualification dispatch, alias, release, runtime or #1099 effect is selected here. General owns the train while both repository agents remain Off. |
|
General #1101 fresh queue T0: 2026-11-08T16:03:25Z, one enqueue with expectedHeadOid E4, under selection 6723733715 / b0799a0c36f85b23de572039a981317d45e9953ccf0e61aeedb7578cefaa93da. Entry MQE_lQDOSATFBs8AAAABNoedCM4ABPZYzgPRFXw, initially QUEUED position 1; ceiling 2026-11-08T16:48:25+00:00. Admission re-read exact: actual main C f77b093, 71 success +8 intended skips /0 statuses; frozen runner/head E4 6754daa, 68 success +1 intended skip /0 statuses, all required checks green; open/ready/MERGEABLE/CLEAN, no auto-merge, empty queue. No runner push/rebase or workflow retry/cancel. Expected parents [C,E4], combined tree 7f1111d38ee58fe3c97fb77a67b7827984dc683d. The runner's sole parent/merge base remains release M; only the subject file changes relative to C. Runner branch is kept. Tag/image 3.3.0 stay at M/D. Watch-only until resolution; one exact dequeue if the same entry is still live at the ceiling. Then signature/parents/combined-tree/ancestry/actual-main terminal custody before any separately selected qualification dispatch. Earlier queue NONPASSs preserved; #1099 deferred. Both repo agents remain Off. |
|
General returns #1101 terminal actual-main custody. Third queue entry merged at 16:25:22Z, inside its 16:48:25Z ceiling; no dequeue, re-entry, cancellation or rerun. Both earlier queue NONPASSs stay attributed. R = b4c11e5 is current main, signed valid. Ordered parents [C f77b093, E4 6754daa], combined tree 7f1111d38ee58fe3c97fb77a67b7827984dc683d, exactly the reviewed combined tree. All 79 checks are terminal: 71 success, 8 expected skips, 0 failures/cancelled/timed-out; 0 statuses. Runner branch is kept at exact E4, which is an ancestor of R. Subject remains 902 B /6d89a8e7, release block 3.3.0 / M 2a15179 / native-release 42460578773 attempt 1 / D cb4b11bd. Tag 3.3.0 is still the commit M. No rebase or source change entered the frozen runner; main R includes C's CI repair through the reviewed merge. No saved WIP ref was touched. Next is a separately selected published-image corpus dispatch on the fixed runner ref with exact ghcr@D; then exact-digest Compose and no-input tag/default Compose. No dispatch, alias or GitHub Release is claimed by this custody receipt. #1099 remains deferred. Both repo agents remain Off; General owns qualification. |
Summary
This points the native qualification runner at the published Native 3.3.0 image. Only the
releaseblock ofscripts/ci/native-qualification-subject.jsonchanges:{"index_digest":"sha256:cb4b11bd6235a551cf51e7dc6342504fbbcef19959618b376fb5648ca00fc388","run_attempt":1,"run_id":42460578773,"source_commit":"2a15179f29801eec9f2a2d4e6a9c5f93233f104e","tag":"3.3.0"}The MySQL and QEMU pins and the schema are unchanged.
6754daa8, tree573b0ea3, with M2a15179fas its only parent.f2a9cf48…. Subject file: 902 B, sha2566d89a8e7….Evidence:
Admission: qualification admission requires this commit to be 1–32 commits ahead of
release.source_commit, to touch only runner paths, and to be contained in main. The main merge queue uses MERGE, which keeps E4 as an ancestor.Status: draft and out of the queue. This PR is only for one normal source CI train. No ready/queue entry, qualification dispatch, alias or release is selected. Local tests were not run because of the local execution stop.
🤖 Generated with Claude Code