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, False, True, True, False, False, True, True, True, False]) 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, False, True, True, False, False, True, True, True, False], ) Unreliable test timings! On an initial run, this test took 574.62ms, which exceeded the deadline of 200.00ms, but on a subsequent run it took 2.64 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'AXicY2RkZABCEIDS7KxAzMbIwAAAAc4AKw==') 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)

test_should_match_prefixed_bytes hypothesis.errors.Flaky: Hypothesis test_should_match_prefixed_bytes(value=b'\x01\x00\xfa', other=b'\x19\x14') produces unreliable results: Falsified on the first call but did not on a subsequent one Falsifying example: test_should_match_prefixed_bytes( value=b'\x01\x00\xfa', other=b'\x19\x14', ) Unreliable test timings! On an initial run, this test took 424.40ms, which exceeded the deadline of 200.00ms, but on a subsequent run it took 0.11 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'AAEFAQF6AAcFATH6AAIBOBkBIhQA') as a decorator on your test case