diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-10-10 10:06:59 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-10-10 10:06:59 +0200 |
| commit | c100de578a49915dfc7ca5c30534ccccfd23d46c (patch) | |
| tree | babfeafbfc028a3935af87619609f23b72e8b936 /packages/meshbay-client | |
| parent | e29617c04ebe3097914fed02e6ce917f48a9dbd6 (diff) | |
| download | meshbay-c100de578a49915dfc7ca5c30534ccccfd23d46c.tar.gz | |
test(hub): wait for a resumed transfer's state, not for 120 ms
The pausable run in test_transfers.py moves in setTimeout(5) chunks, and the
resume test gave it a fixed 120 ms to finish. A setTimeout(5) lasts about
15 ms on Windows' default timer, so the resumed run took 156 ms there and the
test failed with nothing wrong; the 20 ms wait before pausing had the same
thin margin. The run now records how far it got (state.at), and the test
pauses after two chunks and waits for "done", bounded at 2 s. The assertions
are unchanged, and a resume that restarts from zero is still caught (checked
by introducing one in transfers.js).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Diffstat (limited to 'packages/meshbay-client')
0 files changed, 0 insertions, 0 deletions