Files
OmniRoute/tests/unit/services/serviceSupervisorSpawnError.test.ts
Diego Rodrigues de Sa e Souza 3d4f3e4960 test(infra): retry recursive temp-dir removal instead of failing a shard on ENOTEMPTY (#11966) (#11968)
* test(infra): retry recursive temp-dir removal instead of failing a shard on ENOTEMPTY (#11966)

Two shards on release/v3.8.51 went red in one day with the same signature —
"ENOTEMPTY, Directory not empty: /tmp/omniroute-<test>-XXXXXX" — from
combo-same-provider-cascade (Unit Tests fast-path 4/4, on a PR that touches only
.github/) and auth-policy-embeddings-webfetch-7785 (the 20k-test TIA step). Both pass
alone and on re-run: the cleanup races something still writing into the directory
(SQLite WAL/-shm checkpoint, a worker, the backup) and under a loaded hosted runner
the window opens. 1154 test files do their own cleanup with
fs.rmSync(dir, { recursive: true, force: true }); 57 already asked for retries.

One-shot codemod (scripts/ad-hoc/codemod-rm-maxretries.mjs, kept for the record):
every rm / rmSync / rmdirSync option object with `recursive: true` and no
`maxRetries` gains `maxRetries: 5, retryDelay: 100` — Node itself then retries
ENOTEMPTY/EBUSY/EPERM for up to ~0.5 s before giving up. 2243 call sites in 1292
files under tests/, the shared tests/_setup/isolateDataDir.ts exit hook included.
Only the option object changes: no call site, assertion or import is touched.

Validation: prettier and ESLint (with the frozen suppressions) clean on all 1292
files; a random 20-file sample runs green (quota-redis-store hangs identically on
the untouched tree — it needs a Redis on localhost, an environment matter). The
four unit shards on this PR are the full run.

* fix(quality): let check-forgotten-sibling-tests read a 1,000-file diff

The gate shells out to `git diff` through execFileSync with Node's default 1 MB
maxBuffer; the 1,292-file codemod in this PR is the first diff large enough to
overflow it, and the gate died with `spawnSync git ENOBUFS` before comparing
anything. 64 MB is far above any real PR and costs nothing when unused.
2026-08-29 01:17:40 -03:00

93 lines
3.8 KiB
TypeScript
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
/**
* Regression tests for the embedded-services supervisor (ServiceSupervisor).
*
* Bug: when the supervised binary cannot be spawned (ENOENT / EACCES, or a
* non-executable binary such as an ELF on Windows — EFTYPE), the child emits
* the 'error' event — NOT 'exit' — and on Windows spawn() can even throw
* synchronously. The supervisor had no 'error' handler, so it stayed in
* "starting" forever while the HealthChecker kept polling the dead port every
* healthIntervalMs (each probe firing a full ProxyFetch dispatcher+native
* fetch pair, e.g. against a CLIProxyAPI port that will never answer on this
* platform).
*
* Fix under test: the supervisor now (1) handles synchronous spawn() throws
* and the child 'error' event → stops the poller and transitions to "error",
* and (2) transitions to "error" and stops the poller once the health checker
* reports FAILURE_THRESHOLD consecutive failures, including during startup,
* instead of polling the dead endpoint forever.
*
* Run: node --import tsx/esm --import ./open-sse/utils/setupPolyfill.ts --import ./tests/_setup/isolateDataDir.ts --test tests/unit/services/serviceSupervisorSpawnError.test.ts
*/
import { describe, it } from "node:test";
import assert from "node:assert/strict";
import { mkdtemp, writeFile, rm } from "node:fs/promises";
import { tmpdir } from "node:os";
import { join } from "node:path";
import { ServiceSupervisor } from "../../../src/lib/services/ServiceSupervisor.ts";
import type { ServiceConfig } from "../../../src/lib/services/types.ts";
function baseConfig(overrides: Partial<ServiceConfig> = {}): ServiceConfig {
return {
tool: "cliproxy",
port: 0,
spawnArgs: () => ({
command: process.execPath,
args: ["-e", "setTimeout(() => {}, 30_000)"],
env: process.env,
cwd: tmpdir(),
}),
healthUrl: () => "http://127.0.0.1:1/v1/models",
healthIntervalMs: 50,
stopTimeoutMs: 1_000,
logsBufferBytes: 4_096,
...overrides,
};
}
describe("ServiceSupervisor spawn-failure handling", () => {
it("transitions to error and stops polling when the binary cannot be spawned", async () => {
// A plain text file is not an executable: on Windows spawn() throws
// synchronously (EFTYPE/EINVAL); on POSIX the child emits 'error'
// (ENOENT/EACCES). Both paths must land in an explicit error state.
const dir = await mkdtemp(join(tmpdir(), "svc-sup-spawn-"));
const badBinary = join(dir, "not-an-executable.txt");
await writeFile(badBinary, "this is not a runnable binary\n", "utf8");
const supervisor = new ServiceSupervisor(
baseConfig({
spawnArgs: () => ({
command: badBinary,
args: [],
env: process.env,
cwd: dir,
}),
})
);
try {
const status = await supervisor.start();
assert.equal(status.state, "error");
assert.ok(status.lastError, "lastError should describe the spawn failure");
assert.match(status.lastError!, /ENOENT|EACCES|EINVAL|EFTYPE|not recognized|spawn|%1|Win32/i);
} finally {
await rm(dir, { recursive: true, force: true, maxRetries: 5, retryDelay: 100 });
}
});
it("transitions to error after consecutive health failures instead of polling forever", async () => {
const supervisor = new ServiceSupervisor(baseConfig());
try {
// The child runs but never opens a server on the health URL: the
// HealthChecker reaches FAILURE_THRESHOLD (3 × 50ms) and the supervisor
// must surface an explicit error instead of staying "running" with an
// endless poller.
await assert.rejects(supervisor.start(), /Health probe failed|Service failed to start/i);
assert.equal(supervisor.getStatus().state, "error");
assert.ok(supervisor.getStatus().lastError);
} finally {
await supervisor.stop();
}
});
});