Test #1213
test.yml
on: schedule
unit-test
1h 54m
docker-build
35s
Annotations
2 errors and 2 warnings
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', 'p1'], -751.150005),
Search(['p0', 'p1'], -876.8377057435154),
Search(['p0', 'p1'], -0.7529999999999999),
Search(['p0', 'p1'], -823.9741142699678),
Search(['p0', 'p1'], -58.60687945649511),
Search(['p0', 'p1'], 797.5920744051864),
Search(['p0', 'p1'], -753.349995),
Search(['p0', 'p1'], -751.150005)]) 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', 'p1'], -751.150005),
Search(['p0', 'p1'], -876.8377057435154),
Search(['p0', 'p1'], -0.7529999999999999),
Search(['p0', 'p1'], -823.9741142699678),
Search(['p0', 'p1'], -58.60687945649511),
Search(['p0', 'p1'], 797.5920744051864),
Search(['p0', 'p1'], -753.349995),
Search(['p0', 'p1'], -751.150005)],
)
Unreliable test timings! On an initial run, this test took 1220.07ms, which exceeded the deadline of 300.00ms, but on a subsequent run it took 9.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.98.11', b'AXicrVLNS9NxHP68fF+2dK1M0KUJMV9gc64oqzFyToYKURGJRoVlWcvL8BSGgV+C6FIK5aEJiUYnD4FUFE3QjNKDh4ogukhBRnRZxYL08us39kJ/QM/pA5+X5+F5Pij8Eq21ZBZ3XQQ5YGYL7EWeZdQwD1rBQsnoWpNrxCIJRuaGYziHdISZoJWBaiUuvcktO7W9sFHTNvzHO/UAzLlNO/ufrf4KczeqGMlmUnUQUJhn6reL6MZE/dZMxg/mVjp8YfJLTyd+R9WJMk2ae0FGGhVa33Lzboct5s76iUyq9mw5H0JNQagUaPK6HaLYPcxnUIuqYxPlXVGef0pauT9MEnpuH9g8vQhqT6RUwItBKGD4ypgj8a7RCeZm9XFfb82Ty1yPosM+QbFVojIok2B9yrG4ANIv++JHAwsrYC599GxvGH1VigOosWJ8yHH1NEgETJ6q6rk3O/cZTV80PJBc6i4BeOwPNIngSArM9ffV696xxf34E1FOtaKYZkbVDrsVmEc3rCxcophGAuqQXiO3ED0ECkVa/JqgonmFUr9PLoOZSfooNNNhm1rIaRd6EXH8GuwLioLV51kLMOpiFvE2SiDfZ+SDQA2MVj67fz5A0bItbTBkG+f5+nbbkOHn7WRHW+n7oeNu2KGwQMayeNZJaaQu4P/yVPAXQnqoxg==') as a decorator on your test case
|
unit-test
Process completed with exit code 1.
|
docker-build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
unit-test
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3, actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|