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
Seed tool treats any message containing [known candidate: as known #55
tools/oracles.cs seeds counts a failing test as a known candidate whenever its message contains [known candidate: anywhere. When one test method checks several rows, and one of them is a registered candidate, a seed that breaks a different row in the same method reads as "known" instead of "caught". So the seed proof can pass without the oracle having caught the seeded defect.
The probing round worked around it by splitting DecorativeElementContractTests into one method per arity. The tool should match per failing line instead, or refuse a mixed message. Seed the case to prove it.
Moved into the 10.0.0 epic (#58) on 2026-10-18: it lands before #179, whose first step is the seed proof this tool runs. A seed counted as "known" because a different row in the same method is a registered candidate would let the gate pass without the oracle having caught the defect.
Activity
CaffeinatedCoder commentedon Oct 18, 2026
Moved into the 10.0.0 epic (#58) on 2026-10-18: it lands before #179, whose first step is the seed proof this tool runs. A seed counted as "known" because a different row in the same method is a registered candidate would let the gate pass without the oracle having caught the defect.