Skip to content

Qualify the published four-worker queue consumer on 2.5.32 - #837

Merged
rmcdaniel merged 5 commits into
mainfrom
chore/published-queue-2.5.31
Oct 17, 2026
Merged

rmcdaniel merged 5 commits into
mainfrom
chore/published-queue-2.5.31

Conversation

@rmcdaniel

@rmcdaniel rmcdaniel commented Oct 17, 2026 •

Copy link
Copy Markdown
Member

Qualify normally installed Workflow 2.5.32 / 78075b6f with the existing
continuous four-worker consumer on stock hosted PHP 8.3.

  • Select only the published Workflow package and its exact source reference.
    Every other locked package object is unchanged.
  • Pin Ubuntu 24.04 to preserve the fixture's explicitly asserted stock PHP 8.3.
  • Keep all 64 callbacks, four real workers, 90-second observer, 120/100-second
    original deadlines and aggregate 2-CPU / 2-GiB / no-swap limits.
  • Keep the zero-repair, zero-failed-job and drained-transport acceptance guards.
    Bounded failure diagnostics capture row state, native error information and
    admission timing. They do not alter runtime behavior or grant task authority.

Published 2.5.32 passes all 17 release-verification jobs and the six normal
installed regressions / 92 assertions, with all 939 runtime/resource files
matching its immutable tag. Source #838 and compatible backport #839 are merged.

Earlier outcomes remain explicit:

  • 2.5.31 / 7789fc95, run 39064714553, original
    01m55q38dd5jr78nse8e2vseqd: business assertions pass, one repair fails the
    clean guard. No delivery exception was captured.
  • 2.5.31 / 3183e877, run 39065805820: ordinary and diagnostic originals both
    complete all callbacks once, but each retains a failed pre-claim SQLite5
    delivery. Reserved-row observations are pre-update intents, not commit proof.
  • 2.5.32 / e3a04c22, run 39070006619: ordinary original
    01m55vckqxdz5ccksvk4cswm9z completes all 64 callbacks once, with exact output,
    prefix and deadlines, but retains one failed pre-claim SQLite5 delivery and
    one repair. Its task 01m55vcm0nr46tc7gwc1tyvn01 has one logical attempt.
    The fresh diagnostic original 01m55ve07aekzbvq2ek990pstt passes the unchanged
    clean guard. The failed ordinary record stays failed; its precise native error
    type and admission elapsed time were not captured, so its cause is not settled.
  • Diagnostic-only head c903ee31, run 39071079709: the fresh ordinary cohort
    passes all unchanged guards; the failure-only diagnostic is skipped. Normal
    source, Sonar and boundary checks also pass. This result does not explain or relabel the
    earlier failed original, and no further runtime correction is claimed.

The documented repair policy intentionally retains reserved deliveries on its
repair path. That fact does not waive the current clean-consumer criterion.

Merged as a5c0ce94a4bdf66b2c874dce4ea910b16988208c, whole tree
1749ff19ff17cd9acc34d312dcb6e10eb8e3b25f, exactly the qualified candidate.
Parents are qualified main 8f55cdfb and final candidate c903ee31.
The merged remote head is absent.

@sonarqubecloud

Copy link
Copy Markdown

@rmcdaniel rmcdaniel changed the title Qualify the published four-worker queue consumer on 2.5.31 Qualify the published four-worker queue consumer on 2.5.32 Oct 17, 2026
@rmcdaniel
rmcdaniel marked this pull request as ready for review October 17, 2026 21:35
@rmcdaniel
rmcdaniel merged commit a5c0ce9 into main Oct 17, 2026
19 checks passed
@rmcdaniel

Copy link
Copy Markdown
Member Author

Fresh main a5c0ce94a4bdf66b2c874dce4ea910b16988208c now passes all applicable
checks in build 39071561870, plus boundary and CodeQL. Exact main Sonar analysis
6701d643-b5df-4cc0-9da1-56387b36ed5e reports an OK gate, 98.3% new-code coverage,
zero new duplication and no ignored conditions.

The ordinary published four-worker pass remains its own candidate original
39071079709. Earlier failed originals remain failed and their causes are not
reinterpreted. The merged branch and completed local worktree are retired.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants