paldepind/synceddb

Sometimes Testem test fails with timeout

piglovesyou opened this issue · 3 comments

Sometimes Testem test fails with timeout

    ...
not ok 27 Firefox 48.0 - SyncedDB "after each" hook for "puts several already saved records in series"
    ---
        message: >
            timeout of 2000ms exceeded. Ensure the done() callback is being called in this test.
        Log: |
    ...
1..27
# tests 27
# pass  26
# skip  0
# fail  1
npm ERR! Test failed.  See above for more details.
npm ERR! Test failed.  See above for more details.
The command "npm test" exited with 1.
Done. Your build exited with 1.

Should we give a retry count?

I wonder if this is because the test case never finishes or if because executing the test takes longer than 2 seconds. Instead of giving a retry count me might try increasing the time given to each test unit.

Yes if actual duration of the tests takes more than 2 sec we should do that. But I also feel browser testing is not 100% stable. I'll investigate it anyway 👍

Recent builds do not contains this kind of failure. I'll close this for now.