-
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
Build against 2.14.0 #2850
Build against 2.14.0 #2850
Conversation
Need to update as: Same issue reported in #2849 |
Hi @seanpmorgan, TF 2.14 has been released. Any luck with the TF addons build? |
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.
Switch to 2.14.0
WORKSPACE
Outdated
], | ||
) | ||
# TODO: please double check what it is really required or not in this section |
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.
@seanpmorgan This was commited by the bot/proxy GitHub account in the upstream TF WORKSPACE
. Can you ping SIG-Build team to know who is the owner of that new section?
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.
@yongtang is handling the same at tensorflow/io#1831
e6c89eb
to
9297f60
Compare
d897900
to
19f2c37
Compare
2d7a2df
to
554c26f
Compare
Same thing we did against TF2.13 build. Given that we have about ~3 more releases left , I think we can just keep the lights on and not take the bazel workspace dependency on TF2.14 with hermetic python. The custom ops are compiled against TF2.14 as is written to .bazelrc Open to a PR to clean up the build env (will also try to clean it up if I can get some free cycles). tensorflow/build is still publishing a container for each python version so I don't see a huge need to adopt the new build strategy. |
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.
Ok I hope that it will not be mandatory to upgrade the workspace sooner or later.
No description provided.