mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-10-31 02:45:40 +00:00
Miguel Ángel
c610d8491c
* fix(cli): keep the contact sheet png test within its budget on slow runners sharp's bundled Pango/Fontconfig backend enumerates the OS font directories on first text render and builds an on-disk cache before it can draw the sheet's labels. On Windows CI that first-render scan is unbounded (measured 12s-103s here for otherwise-millisecond work), which is what the 60s ceiling was really absorbing. Point Fontconfig at an empty, per-run config on win32 so label rendering has nothing to scan, and bring the budget down to reflect the real raster work. * test(cli): keep the createContactSheet timing label to measure the Windows font fix Diagnostic: the Windows job on this branch prints createContactSheet's wall time with the one-font Fontconfig override, to compare against 3.7-18.4s without it. * test(cli): temporary diagnostic, time the first svg and first svg text render * test(cli): temporary diagnostic, first text render in a child process * test(cli): set the Windows Fontconfig file in the vitest config, before workers start * test(cli): drop the contact sheet timing diagnostics * fix(cli): the vitest Fontconfig dir is created with an unpredictable name and removed on exit
61 lines
2.8 KiB
TypeScript
61 lines
2.8 KiB
TypeScript
import { copyFileSync, mkdtempSync, rmSync, writeFileSync } from "node:fs";
|
|
import { tmpdir } from "node:os";
|
|
import { join, resolve } from "node:path";
|
|
import { defineConfig } from "vitest/config";
|
|
|
|
// Windows: sharp's first text render builds Fontconfig's cache for every OS font (about 9 s on a
|
|
// fresh runner). Set here, before workers fork, because an in-process env write never reaches it.
|
|
if (process.platform === "win32") {
|
|
const dir = mkdtempSync(join(tmpdir(), "hf-vitest-fontconfig-"));
|
|
process.once("exit", () => rmSync(dir, { recursive: true, force: true }));
|
|
copyFileSync(
|
|
join(process.env.WINDIR ?? "C:\\Windows", "Fonts", "arial.ttf"),
|
|
join(dir, "arial.ttf"),
|
|
);
|
|
const file = join(dir, "fonts.conf");
|
|
writeFileSync(
|
|
file,
|
|
`<?xml version="1.0"?><!DOCTYPE fontconfig SYSTEM "fonts.dtd"><fontconfig><dir>${dir}</dir><cachedir>${dir}</cachedir></fontconfig>`,
|
|
);
|
|
process.env.FONTCONFIG_FILE = file;
|
|
}
|
|
|
|
export default defineConfig({
|
|
resolve: {
|
|
alias: [
|
|
// Resolve the bare @hyperframes/core entry to TypeScript source, not built
|
|
// dist. The published dist intentionally omits runtime/entry.ts, so the
|
|
// dist build of loadHyperframeRuntimeSource() returns null — which makes
|
|
// studioServer.test.ts's runtime-source equality assertion diverge. Tests
|
|
// run under bun against source; subpath imports (@hyperframes/core/*) keep
|
|
// resolving via the package's export conditions.
|
|
{
|
|
find: /^@hyperframes\/core$/,
|
|
replacement: resolve(__dirname, "../core/src/index.ts"),
|
|
},
|
|
// Same reason the tsup build aliases this specifier to source: the CLI
|
|
// bundles the producer rather than depending on it at runtime, so its
|
|
// dist is not built for the test job. Without the alias, vite's import
|
|
// analysis resolves studioServer.ts's `import("@hyperframes/producer")`
|
|
// against an unbuilt package and the whole suite fails to collect.
|
|
{
|
|
find: /^@hyperframes\/producer$/,
|
|
replacement: resolve(__dirname, "../producer/src/index.ts"),
|
|
},
|
|
],
|
|
},
|
|
test: {
|
|
include: ["src/**/*.test.ts"],
|
|
// Many CLI tests cold-import a heavy command module graph via dynamic
|
|
// `import()` (e.g. render.js, auth/status.js, telemetry/system.js). Under
|
|
// the full parallel monorepo run (`bun run --filter '!@hyperframes/producer'
|
|
// test`) that cold load contends for CPU and routinely blows vitest's 5s
|
|
// default test timeout / 10s hook timeout on CI runners — a recurring
|
|
// flake that has failed unrelated PRs (see PRs #1843, #1850). These
|
|
// generous ceilings absorb the contention while still catching a genuine
|
|
// hang. Prefer this one config knob over per-test/per-hook timeout bandaids.
|
|
testTimeout: 20_000,
|
|
hookTimeout: 30_000,
|
|
},
|
|
});
|