adam/Remote-Terminal-for-MeshCore
1
0
Fork 0
mirror of https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git synced 2026-07-30 21:43:14 +02:00
Code Issues Packages Projects Releases Wiki Activity

Stabilize app startup hash test timeout

Browse Source
This commit is contained in:
Björkan
2026-07-03 19:02:25 +02:00
parent 55020a5e22
commit 2118c83bc4
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
frontend/src/test/appStartupHash.test.tsx
+6 -6
View File
@@ -154,10 +154,10 @@ const publicChannel = {
// contacts, unreads) that must all settle before conversation selection
// renders. This suite passes in isolation, but under the full parallel suite
// (~70 files) CPU contention can stretch that startup well past RTL's 1000ms
// default — and even past vitest's 5000ms test timeout — for any waitFor in
// this file. It's starvation, not a hang, so give this file generous headroom
// on both timeouts: a healthy render still settles in ~100ms (nothing is
// slowed), only a starved run waits longer.
// default — and occasionally past 10s on GitHub's shared runners — for any
// waitFor in this file. It's starvation, not a hang, so give this file generous
// headroom on both timeouts: a healthy render still settles in ~100ms (nothing
// is slowed), only a starved run waits longer.
//
// These MUST run at module scope, not in beforeAll: vitest bakes each test's
// timeout in when it() registers the test (during collection, before any
@@ -167,8 +167,8 @@ const publicChannel = {
// 10s but the test killed at 5s) that flaked under load. vi.setConfig is scoped
// to this file (each file runs in its own isolated worker), so other files are
// unaffected.
vi.setConfig({ testTimeout: 15000 });
configure({ asyncUtilTimeout: 10000 });
vi.setConfig({ testTimeout: 45000 });
configure({ asyncUtilTimeout: 30000 });
describe('App startup hash resolution', () => {
beforeEach(() => {