Repository navigation
Commit 699b011
committed
ci(bun): put the worker idle-memory limit above what the suite uses
`runtimes (bun)` segfaults at a different wild address each run, on this
branch and on main alike. Reproduced locally with Bun 1.3.14, the CI patches
and the CI command, and it is the idle-memory restart: with the limit below
what the suite uses, workers restart constantly and Bun crashes tearing one
down.
limit vs the suite's heaps result
16MB below segfault, spawned(61) terminated(57)
64MB below segfault, spawned(20) terminated(16)
512MB above 103 suites, 28993 tests, green
2048MB above 103 suites, 28993 tests, green
The last green CI run had no limit at all and finished all 159 suites with
worker heaps reaching 1337 MB. Restoring the limit set it to the 512 MB the
other runtimes use — under half of that — so it fires on workers doing
ordinary work, and the run dies about a third of the way in. Raise it to
2048 MB: above what the suite needs, still a bound on a worker that runs
away. Node and Deno keep 512 MB, where a spurious restart only costs time.
Ending a worker rather than terminating it, as the patch already does, buys
Bun a restart it would not otherwise survive — a small run took five and
passed — but not a run full of them. Both teardown paths crash in bulk, so
the limit is the lever, and the patch is left as it is.1 parent 1b8718b commit 699b011
2 files changed
Lines changed: 4 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
339 | 339 | | |
340 | 340 | | |
341 | 341 | | |
342 | | - | |
| 342 | + | |
| 343 | + | |
| 344 | + | |
343 | 345 | | |
344 | 346 | | |
345 | 347 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
70 | 70 | | |
71 | 71 | | |
72 | 72 | | |
73 | | - | |
| 73 | + | |
74 | 74 | | |
75 | 75 | | |
76 | 76 | | |
| |||
0 commit comments