Repository navigation
Commit 12b26bb
authored
test: retry TestWasm when Chrome does not start in time (#584)
TestWasm failed with "websocket url timeout reached" when Chrome took
more than 20s to print its DevTools address. On 20 fresh GitHub
runners the first Chrome start took 5.2s to 27.4s, and 3 took over
20s. Later starts took at most 1.2s. TestWasm now retries on that
error, up to 3 attempts.1 parent 5d0eacc commit 12b26bb
1 file changed
Lines changed: 17 additions & 7 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
459 | 459 | | |
460 | 460 | | |
461 | 461 | | |
462 | | - | |
| 462 | + | |
463 | 463 | | |
464 | 464 | | |
465 | | - | |
466 | | - | |
467 | | - | |
468 | | - | |
469 | | - | |
470 | | - | |
| 465 | + | |
| 466 | + | |
| 467 | + | |
| 468 | + | |
| 469 | + | |
| 470 | + | |
| 471 | + | |
| 472 | + | |
| 473 | + | |
| 474 | + | |
| 475 | + | |
| 476 | + | |
| 477 | + | |
| 478 | + | |
| 479 | + | |
| 480 | + | |
471 | 481 | | |
472 | 482 | | |
473 | 483 | | |
| |||
0 commit comments