-
Notifications
You must be signed in to change notification settings - Fork 6.5k
[btlr] testing: use NUM_TEST_WORKERS env var #4030
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
Conversation
Seeing lots of failures in py-2.7.
|
Build time lint: 7 min, 54 sec I think we can just go with the default. I'll fix some flakes then try the full build again. |
Now it temporarily includes #4048 All the jobs are just using the default value. |
Build time without setting NUM_TEST_WORKERS (defaut values): lint: 10 min, 36 sec The failure in py-3.8 build is reported at #4054 The builds were rather slow, it might be because of some retries, but it might be because of low number of workers. The last periodic builds are (btlr is using fixed 30 workers): lint: 9 min, 38 sec I'll try 10 workers next. |
Build time with 10 workers: lint: 9 min, 24 sec There were no weird error during |
Seeing a new failure in py-2.7 build:
|
I'll update the number of workers for the py-2.7 build to 1. The build is already fast enough without running in parallel. |
It seems like the failures in py-2.7 build are deterministic. |
https://pypi.org/project/rsa/4.2/#description
I think we need to pin rsa-4.0 for some projects. Update: The new google-auth handles this. |
Some tests still fail in py-2.7 build. |
Build time with 10 workers: lint: 10 min, 0 sec There was only one failure in healthcare, which should be fixed by #4064 |
Restarted py-3.7 build |
Experimenting with different number of workers.
lint, py-2.7, py-3.6:
default (I think it's 6 on Kokoro)
py-3.7:
12
py-3.8:
20