{
  "id": 12969753,
  "title": "A Fixture Hash Separates Deterministic Misses From Eligible Flake Freezes",
  "url": "https://urgent.news/2026/10/08/a-fixture-hash-separates-deterministic-misses-from-eligible-flake",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-08T22:33:46.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/datacpp_8185/a-fixture-hash-separates-deterministic-misses-from-eligible-flake-freezes-23fl"
  },
  "original_language": "en",
  "account": "A property failure on an agent patch is initially considered a miss until proven otherwise through a shrink. Freeze eligibility is determined after the miss is reduced to a minimal input, stored as a hashed fixture, and replayed on both the base revision and candidate. Red-build counts have no impact on this decision. Flaky tests often result from narrow input bugs, while the opposite error is equally detrimental: a test that already fails on the base gets attributed to the patch, and a clean candidate is discarded for unnecessary noise. Three records differentiate between these scenarios. A property check samples a space under a seed, a fixture pins one input and its hash, and a freeze is a time-bounded exception for a single variance class. Eliminate any one of the three, and the label \"flaky\" becomes conjecture. Variance classes, not failure totals, dictate the workflow table, which serves as a decision-making tool rather than a live suite score or benchmark. A minimum of two replays per revision is the classifier's lowest acceptance threshold, not a fixed sample size for every property. The table outlines the necessary steps to determine the appropriate action. To unlock a freeze, only one class must be deemed deterministic_miss, with mixed results on the other classes resulting in a draw that requires a new local seed budget and avoidance of freezing. Any other matching-hash pattern triggers the addition of replays or referral to a human. A mismatch in hash values signals the need for further investigation and discarding of stale files. The process begins by recording the seed before the candidate runs, as a sample without a seed cannot be replayed and thus cannot support a freeze. The property id, seed, and base revision must be bound before the agent edit is applied.",
  "summary": "A property failure on an agent patch is a miss until a shrink proves otherwise. Freeze eligibility is a later question, and it stays closed until that miss is reduced to a minimal input, stored as a hashed fixture, and replayed on both the base revision and the candidate. Red-build counts do not enter the decision. Generated edits often fail one sample and pass the next. That pattern looks like a…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}