Live connection test is flaky, blocking several PRs
See original GitHub issueThe live firebase connection
acceptance test (authored by @steven-ferguson ) is timing out and blocking contributor PRs. It’d be helpful if the maintainers of this repo could either correct or fix this tests so that contributions aren’t blocked or delayed.
Affected PRs:
Error message from Travis CI:
not ok 22 Firefox 51.0 - Acceptance: live firebase connection handles live connections in testing
---
message: >
timeout of 2000ms exceeded. Ensure the done() callback is being called in this test.
stack: >
[35]</</Runnable.prototype.resetTimeout/this.timer<@http://localhost:7357/assets/test-support.js:6326:19
Log: |
...
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Foresight Blog | Detecting Flaky Tests in CI Pipelines
We can easily identify that this is a flaky test and it blocks our CI pipeline. Conclusion. Intermittent failures add time and stress...
Read more >How to Fix Flaky Tests - Semaphore CI
Randomly failing tests are the hardest to debug. Here's a framework you can use to fix them and keep your test suite healthy....
Read more >Testing Overview | Block Editor Handbook
Flaky Tests. A test is considered to be flaky when it can pass and fail across multiple retry attempts without any code changes....
Read more >Flaky tests - GitLab Docs
Flaky tests. What's a flaky test? It's a test that sometimes fails, but if you retry it enough times, it passes, eventually.
Read more >How to avoid Flaky Tests : Methods - BrowserStack
Look at Concurrency : Problems with concurrency often leads to test flakiness. Concurrency issues such as data races, deadlocks, and atomicity ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@erichiggins not dead, undergoing a rewrite. Will have more to announce soon.
I retriggered Travis builds a few times in PR #533 (with identical code each time), just to see if I was unlucky on a given day, but no dice.
Looking back at the build history, it’s very inconsistent as to whether the failure occurs or not. Over the course of three build events, test suites with identical parameters have passed at some times and failed at others. I have yet to get lucky enough for every test suite in a build to pass, though I’m guessing that if I tried for long enough, I would eventually succeed.
Links to my build history: