From 0624b2eaf69975d42840f3a5f7aeb19fd0a23174 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fredrik=20Adel=C3=B6w?= Date: Wed, 13 May 2026 15:21:06 +0200 Subject: [PATCH] fix(backend-defaults): fix flaky TaskWorker initialDelayDuration test MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The "respects initialDelayDuration per worker" test had only a 50ms margin (350ms total sleep vs 300ms initial delay) for the worker to complete its internal DB roundtrips before asserting. Under CI load this frequently wasn't enough. Replace the fixed sleep with waitForExpect, consistent with the rest of the test file. Co-Authored-By: Claude Opus 4.6 (1M context) Signed-off-by: Fredrik Adelöw --- .../src/entrypoints/scheduler/lib/TaskWorker.test.ts | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/packages/backend-defaults/src/entrypoints/scheduler/lib/TaskWorker.test.ts b/packages/backend-defaults/src/entrypoints/scheduler/lib/TaskWorker.test.ts index 2f690ef499..547ec23474 100644 --- a/packages/backend-defaults/src/entrypoints/scheduler/lib/TaskWorker.test.ts +++ b/packages/backend-defaults/src/entrypoints/scheduler/lib/TaskWorker.test.ts @@ -328,8 +328,9 @@ describe.each(databases.eachSupportedId())('TaskWorker, %s', databaseId => { expect(fn1).toHaveBeenCalledTimes(0); await new Promise(resolve => setTimeout(resolve, 250)); expect(fn1).toHaveBeenCalledTimes(0); - await new Promise(resolve => setTimeout(resolve, 100)); - expect(fn1.mock.calls.length).toBeGreaterThan(0); + await waitForExpect(() => { + expect(fn1.mock.calls.length).toBeGreaterThan(0); + }); // Start a second worker and make sure it waits but the first worker still works along const fn2 = jest.fn();