-
Notifications
You must be signed in to change notification settings - Fork 132
CI: update to TF 2.10 #1160
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
CI: update to TF 2.10 #1160
Conversation
Currently fails:
Or:
Or:
Or:
|
GitHub Actions seems to pick up a reasonable GCC version. From test_TFNativeOp:
Other relevant:
|
I don't really understand: Why are some of the seemingly unrelated tests using older TF versions failing now? And also, why with such weird stacktrace? E.g. tf-tests (TEST=TFUtil, 3.7, 1.15.3):
And when you look up Maybe the GitHub CI cache is somehow messing up different TF versions?
In the log I see:
And then:
So Or maybe Numpy version? |
Actually no it does not, at least TF 2.3 and probably all earlier versions: https://github.com/tensorflow/tensorflow/blob/v2.3.0/tensorflow/python/ops/array_ops.py#L2730 |
For comparison, in the current master:
So interestingly it has an older NumPy version. So the newer NumPy version probably causes the error. |
Ok, that old Numpy version was too specific. For Python 2.7, it fails:
|
The PyCharm inspections raise many new warnings for TF 2.10 (see here), for example:
I will just keep the old TF version for the PyCharm inspections for now. We can later look at that. |
No description provided.