Skip to content

0.70.2 T19: RQ-3 CRUX nightly; release day runs no CRUX and refuses a missing smoke cell #4702

Closed as not planned

Description

@noahgift

Row T19 of aprender-a7's 0.70.2 PROPOSE-TICKET list (cop-inbox handoff/0702-propose-tickets.md, 08:24Z section, from C299 "all recommended"; ranking in handoff/0702-delay-rank.md), verbatim:

- T19 RQ-3 CRUX nightly. Release day runs no CRUX. The same smoke judge runs over the nightly full-lane results for H,
      and a missing smoke cell refuses. Waits on R11 #4690 (release ships the binary the night tested). Needs sign-off.
      −85 min per release. Serves B5. K̂ 4.

Done when (brief §3): a contract, a planted falsifier that goes red, a first green on a real PR, and before-and-after numbers.

Train 0.70.2, P0. Owner: aprender-a7. Minted by the cop's clerk under C297 §4 / C298.

Activity

  1. noahgift commented on Oct 4, 2026

    @noahgift
    ContributorAuthor

    Moved to 0.70.3 by operator ruling: the CRUX nightly waits until its Python steps are ported to bash and Rust, because a nightly may not run Python. The port rows go first. The ready branch stays as it is, with no PR.

  2. added this to the 0.71.0 milestone on Oct 8, 2026
  3. added
    P1High priority
    and removed
    P0Critical priority
    on Oct 14, 2026
  4. noahgift commented on Oct 14, 2026

    @noahgift
    ContributorAuthor

    P0 to P1 (2026-10-14 P0 triage): P0 now means it blocks the next release or carries the operator's own words on it; this issue does neither, so it stays on the 0.71.0 milestone at P1. Its 0.70.2 label belonged to a release that has shipped.

  5. noahgift commented on Oct 14, 2026

    @noahgift
    ContributorAuthor

    Folded into #5306 as a checklist row (TRIAGE-100, 2026-10-14): the open-ticket cap is 100, so this ticket is now tracked on that master and closed as not planned. Nothing is lost: reopen it when its work resumes, and an open PR for it reopens it. Pushed branch: build-kaizen/4702-crux-nightly.

    Agent: aprender-clerk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions