Test

fix: `.not` should also wait for conditions (Breaking changes of issue 1982) #3129

Sign in to view logs

Triggered via pull request January 30, 2026 14:29

synchronize #2014

dprevost-LMI:not-should-also-wait-revert-issue-1982

Status Failure

Total duration 1m 58s

Artifacts –

test.yml

on: pull_request

Matrix: linux

Annotations

7 errors

linux (24.x)

Process completed with exit code 1.

test/utils.test.ts > utils > waitUntil > given we should wait for the reverse condition to meet since element state can take time to update (modifier `.not` is true to for reverse condition) > should be pass=true for normal failure > should return true if condition throws but still return true: test/utils.test.ts#L326

AssertionError: expected "vi.fn()" to be called 4 times, but got 5 times ❯ test/utils.test.ts:326:39

linux (20.x)

Process completed with exit code 1.

test/utils.test.ts > utils > waitUntil > given we should wait for the reverse condition to meet since element state can take time to update (modifier `.not` is true to for reverse condition) > should be pass=true for normal failure > should return true if condition throws but still return true: test/utils.test.ts#L326

AssertionError: expected "vi.fn()" to be called 4 times, but got 5 times ❯ test/utils.test.ts:326:39

linux (22.x)

The strategy configuration was canceled because "linux._24_x" failed

linux (22.x)

Process completed with exit code 1.

test/utils.test.ts > utils > waitUntil > given we should wait for the condition to be met (modifier `.not` is not used) > should be pass=false for normal failure > should return false if condition throws but still return false: test/utils.test.ts#L234

AssertionError: expected "vi.fn()" to be called 4 times, but got 5 times ❯ test/utils.test.ts:234:39