zjncs opened a new issue, #5629: URL: https://github.com/apache/rocketmq-dashboard/issues/5629
## Description Four tests across TopicPage and AlertsPage time out (`Test timed out in 20000ms`) intermittently in full parallel runs while always passing in isolation: - `TopicPage.test.tsx` — `opens a clean create dialog after a cancelled edit` (modal open → cancel → re-open → type → submit → waitFor), `clears selected topics when the search scope changes` (types a 13-char search term key-by-key, then re-queries), `moves back from an emptied last topic page after batch deletion` (pagination → select-all → bulk-delete → confirm → 3 waits — the heaviest chain in the file) - `AlertsPage.test.tsx` — `stays on the page after a bulk delete clears a full page while more pages remain` (pagination → header select-all → bulk delete → confirm → 3 waits) Measurements: the create-dialog test passes at **7.1s** when filtered (only a 2.8x margin against the 20s cap); during a machine-slow period the same test failed at **21.9s** and passed 3x reruns afterwards — a thin-headroom, load-dependent overrun, not a logic bug. The same three TopicPage tests timed out in **both** of two consecutive full parallel runs (7 and 9 failures total), i.e. they are the deterministic-under-load subset. ## Expected behavior The four tests need either fewer sequential awaits or explicit timeout headroom: - the create-dialog test's 8-char `user.type` can be a single `fireEvent.change` (the field's intent is the submitted value) - the three heavy chains get an explicit `45000` timeout (vitest's third-arg), documenting their load-sensitivity instead of letting them flake at 20s ## Environment - branch: master (0228dad5) - files: `web/src/pages/instance/__tests__/TopicPage.test.tsx`, `web/src/pages/ops/__tests__/AlertsPage.test.tsx` (test-only) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
