Test de bissection : 90 s de délai au lieu de 30
node / check (pull_request) Successful in 2m35s
CI / ci (pull_request) Successful in 2m35s

7,5 s sur un poste récent, mais autour de 30 s sur le runner Gitea du VPS, même
seul : il échouait une fois sur deux. Le calcul vérifié ne change pas.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-10-01 19:29:47 +02:00
co-authored by Claude Opus 5.5
parent 6fee084d77
commit e1b764ca31
+2 -1
View File
@@ -168,7 +168,8 @@ describe('minimumRangeBetween', () => {
expect(minimumRangeBetween(knotAndChain(), 0, CHAIN_END, 8).rangePc).toBeCloseTo(1, 1);
});
it('stops bisecting where a search gave up, and hands back a range that does work', { timeout: 30_000 }, () => {
// 7,5 s sur un poste récent, autour de 30 s sur le runner Gitea du VPS : 90 s de marge.
it('stops bisecting where a search gave up, and hands back a range that does work', { timeout: 90_000 }, () => {
// Below the chain's own hop of a parsec, the crowd is still one connected piece and larger than
// the budget, so those probes give up. Reading a give-up as "no chain at this range" is what
// used to report ranges up to 29% wider than needed, and went on paying for probes whose