Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Reading custom ranges unit test fails intermittently
See original GitHub issueThe unit tests sometimes fail with the following line in the logs
TEST-UNEXPECTED-FAIL | read custom ranges | Expected 1016315 to equal 32768. Expected 1016315 to equal 507.
We need to investigate why this happens. It only seems to happen on the Linux bot.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Tests that sometimes fail | Hacker News
Unit tests also sometimes fail because of not cleaning up state properly, which only breaks things when tests run in a very specific...
Read more >Unit test fails when running all, but passes ... - Stack Overflow
When I do "Run all", 3 of them will always fail. If I run them one by one using "Run selected test", they...
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 >Why do Apex Unit Test CLASSES sometimes FAIL when all ...
This can sometimes occur and will cause your test class to also fail even if the class or trigger your test class is...
Read more >Flaky tests - GitLab Docs
It's a test that sometimes fails, but if you retry it enough times, it passes, eventually. What are the potential cause for a...
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 Free
Top 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
It’s probably too early to call this fixed just yet, but these particular unit-tests haven’t failed since Google Chrome was updated to version 80 on the bots. (It would be nice if the update actually fixed something, given the now intermittent reference tests 😃
Yes, let’s do that. We haven’t seen it fail since the Chrome updates anymore.