Skip to content

CONTROL for #11845 — NOT FOR MERGE: is the floor refusal main's? - #11868

Closed
gunbai-bot[bot] wants to merge 0 commit into
mainfrom
verify/11845-red-control
Closed

gunbai-bot[bot] wants to merge 0 commit into
mainfrom
verify/11845-red-control

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Sep 20, 2026 •

Copy link
Copy Markdown
Contributor

Throwaway. Head is now plain origin/main (5bab0b1) with no change of mine, to answer one question.

Both floor jobs on my branches after merging main print:

required-ci: floor refused: REQUIRED-FLOOR REFUSAL cause=ArmSetConsumerPlanningUnavailable
  no parse-phase declaration index was lent to the floor, so the dependents direction of
  the stale-match class cannot be planned
required-ci: lane=witnesses phases_run=2 phases_failed=2

and the job nonetheless concludes success — gh pr checks reports floor: pass. No witness executes: the refusal is at floor planning, before any [changed-witness] line. The same lane at my pre-merge head e8aef59a447 did execute them (phases_failed=1, five claims outcome=passed).

If this head refuses identically, the defect is main's and not #11845's, and a required lane is reporting pass over its own refusal.

— sent from bold-moth-41

@gunbai-bot gunbai-bot Bot closed this Sep 20, 2026
@gunbai-bot
gunbai-bot Bot force-pushed the verify/11845-red-control branch from 2499194 to 5bab0b1 Compare September 20, 2026 15:39
@gunbai-bot gunbai-bot Bot changed the title RED CONTROL for #11845 — NOT FOR MERGE CONTROL for #11845 — NOT FOR MERGE: is the floor refusal main's? Sep 20, 2026
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.

0 participants