Test #1857
test.yml
on: schedule
unit-test
2h 29m
docker-build
54s
Annotations
2 errors
unit-test:
tests/unit_tests/test_matchmaker_algorithm_stable_marriage.py#L130
test_matching_graph_symmetric[build_fast]
hypothesis.errors.Flaky: Hypothesis test_matching_graph_symmetric(request=<FixtureRequest for <Function test_matching_graph_symmetric[build_fast]>>, caplog_context=make_caplog_context, build_func=build_fast, searches=[Search(['p0'], -1500.0),
Search(['p0'], -3.336333333333333),
Search(['p0'], -291.1883330461335),
Search(['p0'], -6.000030000000001),
Search(['p0'], -0.003000000000000001)]) produces unreliable results: Falsified on the first call but did not on a subsequent one
Falsifying example: test_matching_graph_symmetric(
request=<FixtureRequest for <Function test_matching_graph_symmetric[build_fast]>>,
caplog_context=make_caplog_context,
build_func=build_fast,
searches=[Search(['p0'], -1500.0),
Search(['p0'], -3.336333333333333),
Search(['p0'], -291.1883330461335),
Search(['p0'], -6.000030000000001),
Search(['p0'], -0.003000000000000001)],
)
Unreliable test timings! On an initial run, this test took 595.98ms, which exceeded the deadline of 300.00ms, but on a subsequent run it took 2.67 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.6', b'AXicY2AUZ2RkgAJedlYYm/GLH1M5IzszAzMjG8MHBjZGOUbGA1KrwICLnYmRoYE1+dKbiU0M+QzbGVkYDBlZGWYxA5WJMjMy/H86EwRmMDMwNEyWO1MVmqPG0JDhbHTXx4MjgvkMyNQioHofZmZGJoZbQE2CIE0XIBazAJ3QIPLIdPFTBgZThk6g7XXMQAvUgRo6GRi1GRlhpnMCNR2Y/TPiy26VBHYmH0ZGjmuJQNXdzMwg9W8YGABDOjFG') as a decorator on your test case
|
unit-test
Process completed with exit code 1.
|