-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
The PostCommit Python Dependency job is flaky #30799
Comments
Looks better now: https://github.com/apache/beam/actions/workflows/beam_PostCommit_Python_Dependency.yml?query=branch%3Amaster . Close this. |
Reopening since the workflow is still flaky |
|
Reopening since the workflow is still flaky |
|
Should this be escalated to a clearer bug about incompatibility with Tensorflow 2.12? Is it new and reproducible? |
|
@damondouglas @liferoad each have a Python-related commit in there. |
Confirmed by random inspection that the Tensorflow 2.12 variant is always the failure, and always due to timeout. |
I suspect some race conditions when we save the models withe the same name. Will try to do some fixes later. |
The past successful job has this:
The recently failed one has:
Very strange. |
That test environment is defined here Even the 2.18.0 job is wrong, this test environment is supposed to be pinned to TF 2.12 |
Green for the last two weeks. |
The PostCommit Python Dependency is failing over 50% of the time
Please visit https://github.com/apache/beam/actions/workflows/beam_PostCommit_Python_Dependency.yml?query=is%3Afailure+branch%3Amaster to see the logs.
The text was updated successfully, but these errors were encountered: