test_resolve_should_return_if_any_conjecture_resolves_truly hypothesis.errors.Flaky: Hypothesis test_resolve_should_return_if_any_conjecture_resolves_truly(return_values=[True, False, True, True, True, True, True, True, True]) produces unreliable results: Falsified on the first call but did not on a subsequent one Falsifying example: test_resolve_should_return_if_any_conjecture_resolves_truly( return_values=[True, False, True, True, True, True, True, True, True], ) Unreliable test timings! On an initial run, this test took 558.87ms, which exceeded the deadline of 200.00ms, but on a subsequent run it took 1.03 ms, which did not. If you expect this sort of variability in your test timings, consider turning deadlines off for this test by setting deadline=None. You can reproduce this example by temporarily adding @reproduce_failure('6.82.7', b'AXicY2RkZGBEAmxAPgAA6AAY') as a decorator on your test case

test_should_match_when_attribute_value_matches hypothesis.errors.Flaky: Hypothesis test_should_match_when_attribute_value_matches(value='u', other=19711) produces unreliable results: Falsified on the first call but did not on a subsequent one Falsifying example: test_should_match_when_attribute_value_matches( value='u', other=19711, ) Unreliable test timings! On an initial run, this test took 433.42ms, which exceeded the deadline of 200.00ms, but on a subsequent run it took 0.42 ms, which did not. If you expect this sort of variability in your test timings, consider turning deadlines off for this test by setting deadline=None. You can reproduce this example by temporarily adding @reproduce_failure('6.82.7', b'AAEuAAcGAwIAmf4=') as a decorator on your test case

[pylint] tests/unit/test_instance_of.py E: 14,10: unsupported operand type(s) for | (unsupported-binary-operation)