Recorded reproduction

truefoundry/trueforge#417

This page is the executed record, not a fixture. Every run below ran against @truefoundry/trueforge-core@0.1.4. The numbers are what the runs returned.

Verdict
REPRODUCED
Captured
2026-08-29 08:32:26 UTC
Integrity
sha256 a8bb5dd22e083782bd7782fccb0a1343b59fc77ea8525b6358fecc9b5b8baffa

The hash is recomputed by CI on main and on every pull request: pnpm --filter @verdict/agent verify:runtime-evidence

The contrast is the evidence

A condition that fails every time is only meaningful next to one that never does. Both ran the same command the same number of times.

daytona-stalled-endpoint

10 of 10

REPRODUCTION_PINNED

daytona-responsive-endpoint

0 of 10

NOT_REPRODUCED

daytona-stalled-endpoint

REPRODUCTION_PINNED, 10 of 10 runs matched

RunOutcomeExitDurationObserved
stalled-01FAIL_MATCHnone1003 msPOST /snapshots observed; provider call remained pending for 1000 ms
stalled-02FAIL_MATCHnone1001 msPOST /snapshots observed; provider call remained pending for 1000 ms
stalled-03FAIL_MATCHnone1001 msPOST /snapshots observed; provider call remained pending for 1000 ms
stalled-04FAIL_MATCHnone1000 msPOST /snapshots observed; provider call remained pending for 1000 ms
stalled-05FAIL_MATCHnone1001 msPOST /snapshots observed; provider call remained pending for 1000 ms
stalled-06FAIL_MATCHnone1001 msPOST /snapshots observed; provider call remained pending for 1000 ms
stalled-07FAIL_MATCHnone1002 msPOST /snapshots observed; provider call remained pending for 1000 ms
stalled-08FAIL_MATCHnone1001 msPOST /snapshots observed; provider call remained pending for 1000 ms
stalled-09FAIL_MATCHnone1002 msPOST /snapshots observed; provider call remained pending for 1000 ms
stalled-10FAIL_MATCHnone1000 msPOST /snapshots observed; provider call remained pending for 1000 ms
The command every run executed
cd /tmp/verdict-source && printf '%s  %s\n' 'f9962816270aa063020bc616d1d984ff65996f929324ec17ddc78f906894bb06' '/tmp/verdict-source/verdict-reproduction.mjs' | sha256sum -c - && /opt/verdict-node/bin/node /tmp/verdict-source/verdict-reproduction.mjs

Against commit 506bf5c4d1540fa7cb086f1fb697bbe66d1ea5d4

daytona-responsive-endpoint

NOT_REPRODUCED, 0 of 10 runs matched

RunOutcomeExitDurationObserved
responsive-01PASS06 msPOST /snapshots observed; provider resolved with state active
responsive-02PASS02 msPOST /snapshots observed; provider resolved with state active
responsive-03PASS01 msPOST /snapshots observed; provider resolved with state active
responsive-04PASS01 msPOST /snapshots observed; provider resolved with state active
responsive-05PASS01 msPOST /snapshots observed; provider resolved with state active
responsive-06PASS01 msPOST /snapshots observed; provider resolved with state active
responsive-07PASS01 msPOST /snapshots observed; provider resolved with state active
responsive-08PASS01 msPOST /snapshots observed; provider resolved with state active
responsive-09PASS01 msPOST /snapshots observed; provider resolved with state active
responsive-10PASS01 msPOST /snapshots observed; provider resolved with state active
The command every run executed
cd /tmp/verdict-source && printf '%s  %s\n' 'f9962816270aa063020bc616d1d984ff65996f929324ec17ddc78f906894bb06' '/tmp/verdict-source/verdict-reproduction.mjs' | sha256sum -c - && /opt/verdict-node/bin/node /tmp/verdict-source/verdict-reproduction.mjs

Against commit 506bf5c4d1540fa7cb086f1fb697bbe66d1ea5d4