You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In all cases the tests are all passing, but Vitest fails the test run if any errors are thrown after the test environment is torn down.
⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯
Vitest caught 1 unhandled error during the test run.
This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.
⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
Unknown Error: bad theirHave: error loading have at index 0: bad bloom: the value was not a Uint8Array
This error originated in "packages/automerge-repo/test/remoteHeads.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
This error was caught after test environment was torn down. Make sure to cancel any running tasks before test finishes:
- cancel timeouts using clearTimeout and clearInterval
- wait for promises to resolve using the await keyword
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Test Files 15 passed (15)
Tests 164 passed (164)
Errors 1 error
I haven't been able to reproduce the failure locally, so it may have something to do with the CI runner being a bit slower than my laptop. This bit in the setup function looks suspicious to me:
The test action failed twice on #274, and passed the third time I ran it:
❌ Attempt #1
❌ Attempt #2
✅ Attempt #3
In all cases the tests are all passing, but Vitest fails the test run if any errors are thrown after the test environment is torn down.
I haven't been able to reproduce the failure locally, so it may have something to do with the CI runner being a bit slower than my laptop. This bit in the setup function looks suspicious to me:
automerge-repo/packages/automerge-repo/test/remoteHeads.test.ts
Lines 89 to 96 in b87785a
There are similarly arbitrary pauses in the tests themselves:
automerge-repo/packages/automerge-repo/test/remoteHeads.test.ts
Lines 112 to 116 in b87785a
The text was updated successfully, but these errors were encountered: