You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
types ratchet: t27b conformance fixture postfix_optional.t27 redefines Point and Reply (Refs #7437) #7522
Since #7462 (92e2e44, 2026-10-07 11:32Z), specs/tri/t27b/conformance/postfix_optional.t27 defines const Point = struct { x: i32, y: i32 } and const Reply = struct { ok, note, code, at }.
Point is already defined in specs/tri/math/bezier.t27 with f64 fields.
Reply is already defined in specs/compiler/zig_field_syntax.t27 with an error field.
tri types ratchet reports Reply as a NEW conflict on master. Once the port rename for #7437 lands, it reports Point too.
Conformance fixture type names must be unique in the corpus (Q66), as in #7315. Fix: give the fixture's two structs fixture-unique names. The behaviour is unchanged, so the t27b expectation row stays pass.
Reopened 2026-10-07: the bulk close of issues without a ## Boundary section was reverted by the owner. Nothing to do here; this comment replaces the earlier close notice.
An attempt claimed this issue on 2026-10-07 and left an empty branch. A dispatch row that has spent its retry ceiling is released once and then keeps its issue for good, which is the right rule for a third identical failure and the wrong outcome for an issue nobody ever attempted twice. The new issue carries the same work, the same boundary, and today's brief.
Closing this one so the swarm can take the work again.
Activity
gHashTag commentedon Oct 7, 2026
Reopened 2026-10-07: the bulk close of issues without a
## Boundarysection was reverted by the owner. Nothing to do here; this comment replaces the earlier close notice.specs(t27b conformance): fixture-unique names PostfixPoint and Postfi…
github-actions commentedon Oct 18, 2026
Re-filed as #10334.
An attempt claimed this issue on 2026-10-07 and left an empty branch. A dispatch row that has spent its retry ceiling is released once and then keeps its issue for good, which is the right rule for a third identical failure and the wrong outcome for an issue nobody ever attempted twice. The new issue carries the same work, the same boundary, and today's brief.
Closing this one so the swarm can take the work again.