-
Notifications
You must be signed in to change notification settings - Fork 613
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
Make the tests faster #1143
Comments
Most of the offenders tend to be from |
List of the slower tests (>20s):
|
|
I replace divide op with constant for |
Can this be closed as the highest test times have been reduced? For the long term fix of reporting high test times in PRs perhaps we create a new issue? |
Yes, let me open another issue concerning the monitoring of test times before closing this one. I'll do that after the pytest PR is merged. |
A small note, all our tests are decorated with tf.function (because of the By making the graphs of only the functions being tested we can save a lot. I believe that #1288 will make our tests much faster .I did some early speed tests and some of our most time consuming tests are 10x faster in eager mode, which proves that we need to trace only what's needed. |
Describe the bug
Currently, the tests take around 600s. But only a few tests take the majority of this time. The short term solution is to make those specific tests shorter, the long term solution is to put a specific solution in place to monitor the changes in test time and have automatic report of new long tests/tests which became much longer after a change.
Here are the current number from the linux build in the master branch:
As you can see some tests are quite long. If we add more and more feature with the time and we don't monitor tests duration, we'll end up with a build which takes hours to run.
In short:
In the short term, make the tests faster, help is welcome, it's easy to do. Each test often have one task to do, everything done outside the scope of this task can be removed.
Long term: We need a reporting on what changed in the tests duration (likely a bot saying on the pull request if there are changes in term of running time).
The text was updated successfully, but these errors were encountered: