Files
computer-playbook/tests/external
kevinveenbirkenbachandClaude Opus 5 663f144b9a test(external): confirm a failing URL status with a second probe
Two gate runs and a CI workspace job each reddened on a single opencollective funding link from package-lock.json, and all three URLs answered 200 on every later probe. A one-off 4xx from a third-party host is not a broken reference, so the suite now repeats such a probe once after a pause, the way _probe_canary already treats an unreachable canary. A status that repeats still fails, and a transport error is not retried because it is already only a warning.

The retry runs inside the worker that owns the URL, so the pool keeps its concurrency: the added wall-clock is one pause per wave of failures, and the runs measured 84s and 88s against 100s without it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-03 09:35:04 +02:00
..

External Tests 🌐

See external.md for the SPOT: scope, live-dependency rules, and make test-external usage.