Test #1850
test.yml
on: schedule
unit-test
2h 9m
docker-build
46s
Annotations
2 errors
unit-test:
tests/unit_tests/test_matchmaker_algorithm_stable_marriage.py#L153
test_stable_marriage_produces_symmetric_matchings[build_full]
hypothesis.errors.Flaky: Hypothesis test_stable_marriage_produces_symmetric_matchings(request=<FixtureRequest for <Function test_stable_marriage_produces_symmetric_matchings[build_full]>>, caplog_context=make_caplog_context, build_func=build_full, searches=[Search(['p0'], -0.003),
Search(['p0'], -0.003010000000000001),
Search(['p0'], -3.0029999999999997),
Search(['p0'], -1.0),
Search(['p0'], -1.99999)]) produces unreliable results: Falsified on the first call but did not on a subsequent one
Falsifying example: test_stable_marriage_produces_symmetric_matchings(
request=<FixtureRequest for <Function test_stable_marriage_produces_symmetric_matchings[build_full]>>,
caplog_context=make_caplog_context,
build_func=build_full,
searches=[Search(['p0'], -0.003),
Search(['p0'], -0.003010000000000001),
Search(['p0'], -3.0029999999999997),
Search(['p0'], -1.0),
Search(['p0'], -1.99999)],
)
Unreliable test timings! On an initial run, this test took 1013.10ms, which exceeded the deadline of 300.00ms, but on a subsequent run it took 5.09 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'AXicY2DkZGB8EZp5OXeLcgMHEyPDgck/I77sVkkoYRRgZJBkZGMIYGBlVGBhZDzI8TGnUOriJ05WoKLZEEV8TKsZWRmOMLIz5DMwijEy/H/BAAZcLIwMDazJl95MbGKIZqphZJjKBFT3l4mRkVOhjoGZkY0ZaAZEKQMrEtubOZGRhSGSgYlRlpHxAHffUz3e+v/sQHmpVWAgxPSWkYmhipGdjVFyzzMW3UhGZgZ+BgYAK6QuEQ==') as a decorator on your test case
|
unit-test
Process completed with exit code 1.
|