{
  "id": 7332772,
  "title": "My build finished in 0 seconds and thirteen test suites passed. They had run yesterday's binary.",
  "url": "https://urgent.news/2026/09/14/my-build-finished-in-0-seconds-and-thirteen-test-suites-passed-they",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-14T14:03:36.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/mahirhir/my-build-finished-in-0-seconds-and-thirteen-test-suites-passed-they-had-run-yesterdays-binary-3p71"
  },
  "original_language": "en",
  "account": "The verification process for this project requires the source to be moved to a Linux environment, where it can be built and tested. On this particular day, the build process completed in zero seconds, with all thirteen control suites passing. However, this outcome was due to the build tool encountering a stale binary and determining that no changes needed to be made, as it relied solely on timestamps to assess file freshness. The pipeline consisted of numerous checks, but lacked a mechanism to identify this specific issue. The determinism control, which ran each test suite twice and compared the outputs, did not detect the stale binary problem. Instead, it confirmed the deterministic nature of the stale binary, as its contents remained unchanged. The root cause of the failure was the mirror step that preserved source timestamps, which led the build tool to believe the files were up-to-date. To address this, a simple solution is to update the source file timestamps to the current time after the mirror step, making the build tool aware of the actual file modification times. Alternatively, the pipeline could be modified to assert that the build consumed the sources it was given, either by setting the build duration to zero or by ensuring every artifact's modification time matches the mirror's start time.",
  "summary": "The verification step for this project cannot run where the source lives. The toolchain is unusable on that filesystem, so the pipeline mirrors the tree onto a Linux volume and builds there, then runs the control suites against what it built. That day the log read: BUILD exit=0 seconds=0 Then thirteen control suites, every one green, and each one run twice with byte-identical output. Nothing in…",
  "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."
}