mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-10-20 11:02:35 +00:00
84cf629bec
The scheduled full sweep ran unit, vitest, integration and the package build as one Promise.all wave. The 2026-10-18 (omni-build) and 10-19 (omni-release) sweeps killed unit, integration and the build at their ceilings inside it. On 10-19 the webpack build (14-16 GB) pushed the 8-core, 20 GB omni-release slot past memory.high: the kernel throttled every lane and the app's resourcePressure guard, reading that cgroup, answered 503 inside unit tests (three false reds that pass in isolation on the tip). Both days the single unit process at --test-concurrency=4 had run ~29k of its ~32k tests at its 80 min ceiling, while ci.yml runs the same suite as 8 shards of 11-18 min. Unit now runs ci.yml's own shards (npm run test:unit:ci:shard, TEST_SHARD=i/N with N read from ci.yml's test-unit matrix), one per four cores of availableParallelism() (which honours the slot's cpu.max: 2 at a time on omni-release), each under a 40 min ceiling; integration, vitest and the package build follow, one at a time. Each lane is reported as it ends, and a failed shard is named in the gate detail, so a timed-out shard no longer surfaces a fixture's SQLITE_CANTOPEN line as the cause. Refs #15306 |
||
|---|---|---|
| .. | ||
| ad-hoc | ||
| build | ||
| check | ||
| ci | ||
| cli | ||
| compression | ||
| compression-eval | ||
| dev | ||
| devin-bridge | ||
| docker | ||
| docs | ||
| features | ||
| homolog | ||
| i18n | ||
| ops | ||
| packs | ||
| perf | ||
| quality | ||
| release | ||
| research | ||
| router-eval | ||
| skills | ||
| sre | ||
| test | ||
| vps | ||
| check-permissions.sh | ||
| postinstall.mjs | ||
| start-ws-server.mjs | ||