From 215dfc3418052b6c99927e8b41ea2745f36973cf Mon Sep 17 00:00:00 2001 From: ghostcoder42 Date: Sat, 5 Sep 2026 07:28:14 +0800 Subject: [PATCH] fix: stop update-dialog test from timing out on slow CI runners MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The first post-merge CI run on main failed with 'Exceeded timeout of 5000 ms' in update-dialog.test while the identical PR run and local runs were green — the Modal tree flushes asynchronously through act() and a 2-core hosted runner under parallel-suite load can push that past jest's default 5s. Raise this file's timeout to 15s; structure unchanged. --- src/components/update-dialog.test.tsx | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/components/update-dialog.test.tsx b/src/components/update-dialog.test.tsx index 15161ec..255e112 100644 --- a/src/components/update-dialog.test.tsx +++ b/src/components/update-dialog.test.tsx @@ -2,6 +2,13 @@ import type { LatestRelease } from '@/lib/updates'; import { fireEvent, render } from '@testing-library/react-native'; import { UpdateDialog } from './update-dialog'; +// The Modal tree flushes asynchronously through act(); on slow CI runners +// (2-core GitHub hosted machines, suites running in parallel) that can push +// a test past jest's default 5s timeout even though nothing is wrong — that +// is exactly how the first post-merge CI run failed while the PR run, local +// runs and every retry since have been green. Give this file headroom. +jest.setTimeout(15000); + const release: LatestRelease = { version: '0.3.0', releaseUrl: 'https://github.com/ghostcoder42/hanime1/releases/tag/v0.3.0',