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.

Random failures in CrawlTestCase.test_fixed_delay

See original GitHub issue

On some test runs CrawlTestCase.test_fixed_delay fails with

>       yield self._test_delay(total=3, delay=0.1)
E   twisted.trial.unittest.FailTest: twisted.trial.unittest.FailTest: True is not false : test total or delay values are too small

Issue Analytics

State:
Created 4 years ago
Comments:15 (14 by maintainers)

Top GitHub Comments

1reaction

Gallaeciocommented, Feb 24, 2020

It should be a “simple” matter of increasing the parameters of the corresponding tests, using the minimum values that do not cause the tests to fail.

1reaction

wRARcommented, Feb 19, 2020

@sakshamb2113 sure

Top Results From Across the Web

RANDOM, SYSTEMATIC, AND COMMON CAUSE FAILURE

While random failures are caused mainly by physical factors, systematic failures are the direct consequence of device and SIF complexity. Every ...

How to deal with random test failure | Core change policies

What to do if you encounter a random test failure.

Random Failure vs. Systematic Failure: Through the Looking ...

A systematic failure is caused by human error. By contrast, random hardware failures “just happen” in a way that is not deterministic and...

Random versus Systematic Failures – Issues and Solutions

It was decided that random failures are counted in the probabilistic failure rate analysis and systematic failures are not counted. Systematic failures were ......

Are All Random Failures Systematic? - EngineerZone Spotlight

This leads to the question – is there any such think as a random failure or are all failures systematic if you look...