-
Notifications
You must be signed in to change notification settings - Fork 985
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increase timeout of a flaky speed test #5756
Conversation
Avoid flaky GitHub CI failures of Pytest MacOS (3.7).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with one comment. Good to merge once it's addressed.
@@ -4652,11 +4652,16 @@ def test_create_speed(): | |||
# Previously this took ~30s to run. Now it should take ~150ms. However the coverage test can | |||
# run this slowly, so allowing 2 sec to account for things like that. Feel free to increase the | |||
# buffer time or delete the test entirely if it ends up causing flakes. | |||
# | |||
# Updated in https://github.com/quantumlib/Cirq/pull/5756 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a performance regression. Could you file an issue and link to the issue instead of the PR? This way we're not going to loose track of the regression while avoiding the flaky failures for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack - I have added a printout of the actual test durations locally on my linux box, which was
$ echo ' print("\\nDB: elapsed_time =", time.perf_counter() - t)' >> cirq-core/cirq/circuits/circuit_test.py
$ check/pytest -s -n 0 --cov --cov-config=dev_tools/conf/.coveragerc cirq-core/cirq/circuits/circuit_test.py -k test_create_speed | grep DB:
DB: elapsed_time = 0.4660000840012799
- 0.48 s at ef40777 which introduced test_create_speed()
- 0.47 s at this PR
There is no significant change in test time - the failing CI is more likely due to fluctuating loads on the test machines.
Increase timeout of `circuit_test.py::test_create_speed` from 2 to 4 seconds. Avoid flaky test failures of the GitHub CI Pytest MacOS (3.7).
Increase timeout of
circuit_test.py::test_create_speed
from 2 to 4 seconds.Avoid flaky test failures of the GitHub CI Pytest MacOS (3.7).