Skip to content

chore(deps-dev): bump hypothesis from 6.82.7 to 6.90.0 #168

chore(deps-dev): bump hypothesis from 6.82.7 to 6.90.0

chore(deps-dev): bump hypothesis from 6.82.7 to 6.90.0 #168

Triggered via pull request November 20, 2023 21:51
Status Failure
Total duration 3m 5s
Artifacts

tests.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors
tests: tests/unit/test_all_of.py#L14
test_resolve_should_resolve_if_all_conjectures_resolves_truly hypothesis.errors.Flaky: Hypothesis test_resolve_should_resolve_if_all_conjectures_resolves_truly(return_values=[False, False, False, False, True, False, False, True, True, True, False, False, False, True, True, False]) produces unreliable results: Falsified on the first call but did not on a subsequent one Falsifying example: test_resolve_should_resolve_if_all_conjectures_resolves_truly( return_values=[False, False, False, False, True, False, False, True, True, True, False, False, False, True, True, False], ) Unreliable test timings! On an initial run, this test took 398.28ms, which exceeded the deadline of 200.00ms, but on a subsequent run it took 1.92 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.90.0', b'AXicJcnBDQAgCMDAVkH23xiI6etS8WdKXQl9C0OO5K4azqUBBrAAUw==') as a decorator on your test case
tests
Process completed with exit code 2.