Skip to content

Wave 683: one mistake in two copies, and a withdrawn explanation - #8509

Open
gHashTag wants to merge 2 commits into
masterfrom
queen-2118
Open

gHashTag wants to merge 2 commits into
masterfrom
queen-2118

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #2118

Written by a bee on queen-2118 and published by tools/queen/publish.py. The branch itself is the bee's; the second commit is the coordination entry every pull request must add, which a bee has no way to know about.

1 file changed, 10 insertions(+)

🤖 Generated with Claude Code

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-10 10:48:33 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 50
PRs with All Checks Green 0
READY 0
FAILING 50
PENDING 0
NO CHECKS YET 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=bd3352ccb90e != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@tri-claw tri-claw Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewer bee verdict for head 02de9015132b5e70f95064c992c06d3735ebcf47 (tools/bees/reviewer.py, zai glm-4.7-flash, glm-4.5-flash, 5 turns, 163 s).

BEE-VERDICT: REQUEST_CHANGES
summary: Records Prop. 173d withdrawal correctly but introduces test duplication
criterion: cat tools/withdrawn.txt` contains the withdrawal entry for Prop. 173d and exits 0 -- met -- tools/withdrawn.txt:22-30
discounted-check: Corpus ratchet (expected-failure ledger) -- red on master (master 3b69b91) for the same reason
discounted-check: coverage -- red on master (master c494cc5) for gen-drift issues
blocking-check: duplicate-bodies -- crc_byte and crc_step test bodies were duplicated from 2 to 3 copies

Evidence

Based on my analysis:

Evidence

The pull request successfully addresses issue #2118 by recording the withdrawal of Prop. 173d's explanation in tools/withdrawn.txt. The withdrawal entry is present and contains all required information:

  • The regex pattern for the withdrawn claim
  • Explanation that the stderr capture failure cannot be reproduced
  • Confirmation that the fix (removing -q and redirecting output to a file) stands on its verification
  • Reference to issue #2118 with the correct date

The success criterion is met: cat tools/withdrawn.txt contains the withdrawal entry for Prop. 173d and would exit 0.

Regarding the red checks:

  1. Corpus ratchet (expected-failure ledger) - This check is red on master (master 3b69b91) for the same reason (2 files gained assertionless tests), so it should be discounted.

  2. duplicate-bodies - This check failed because crc_byte and crc_step tests were copied from [2] to [3] copies. Since this check was green on master (c494cc5), the head introduced a real defect by duplicating test bodies.

  3. coverage - This check is red on master (c494cc5), so it should be discounted.

The change properly records the withdrawal within the boundary specified (tools/withdrawn.txt), but introduces a defect by duplicating test bodies.

This was referenced Oct 12, 2026

This branch has not been deployed

No deployments
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.

Wave 683: one mistake in two copies, and a withdrawn explanation

2 participants