Recordsgolanggithub.com/remyoudompheng/bigfftfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
panic: test timed out after 10m0s · running tests: · TestImageBaseMatchesTheRealImage (10m0s) · TestImageBaseMatchesTheRealImage/denoland/deno:alpine (9m58s)
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-08-27 · Last seen: 2026-08-27
sha256:2eb2ea176f55…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-27 → 2026-08-27
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_TEST.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/remyoudompheng/bigfft v0.0.0-20230129092748-24d4a6f8daec: multiply large big.Int numbers using bigfft.Mul This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWbigfft.Mul MIT-0 · 2026-08-18