syntaqxThe runner's long-wait test no longer depends on how fast the machine is. 38a19cb9 let a busy machine write a line for every 50 ms the wait really took, but the work still slept a fixed 180 ms, so on a machine slow enough to answer before the second 50 ms timer fired the log said it once and the test failed the other way. The work now answers once the log has told of the wait twice (a minute at most), so there are always at least two lines, and still never more than one per 50 ms the wait took. Checked: the test 50 times in a row, and cargo test -p g1t-runner (249 passing).5fd6a02History
- ..
- backup-restore-drill.mjs
- backup-restore-drill.test.mjs
- fork-storage-test.mjs
- gitstore-namespaces.mjs
- gitstore-namespaces.test.mjs
- gitstore-usage.mjs
- platform-usage.mjs
- platform-usage.test.mjs
- restore-to-gitstore.mjs
- restore-to-gitstore.test.mjs
- runner-errors.mjs
- runner-errors.test.mjs
- smoke.mjs
- smoke.test.mjs
- sudo.mjs
- vapid-keys.mjs