-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
WIP: Bump to 2.12 + add aarch64 #301
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe:
|
@conda-forge-admin, please rerender. |
…nda-forge-pinning 2023.02.13.17.41.30
Seems like we'll need to wait until the release of tensorflow 2.12 (as we only have tensorboard 2.12 for aarch64). This is scheduled to happen at the end of this month: https://discuss.tensorflow.org/t/when-will-tensorflow-2-12-be-released/14717 |
Can you target the r2.12 branch? And for the sake of resources, let's try to turn off everything else? Do you want me to do it? |
something like this maybe: source:
- git_url: https://github.com/tensorflow/tensorflow/
git_tag: r2.12
- git_url: https://github.com/tensorflow/estimator/
git_tag: r2.12
folder: tensorflow-estimator
#
# - url: https://github.com/tensorflow/tensorflow/archive/refs/tags/v{{ version.replace(".rc", "-rc") }}.tar.gz
# sha256: 99c732b92b1b37fc243a559e02f9aef5671771e272758aa4aec7f34dc92dac48
# patches:
# - patches/0001-loosen-requirements.patch
#
# - url: https://github.com/tensorflow/estimator/archive/refs/tags/v{{ estimator_version.replace(".rc", "-rc") }}.tar.gz
# sha256: 922f9187de79e8e7f7d7a5b2d6d3aabc81bbbd6ba5f12a4f52967dd302214a43
# folder: tensorflow-estimator
like we do in pytorch: https://github.com/conda-forge/pytorch-cpu-feedstock/blob/main/recipe/meta.yaml |
Yes please, go for it! |
Note that we'll need to update keras as well .. |
Yeah, but keras is just a run dep, what we are interested in here is catching serious issues in the compilation. In the first 10 hours of the build or so 🤣 |
Oops, I forgot we have keras in host… well… |
1 similar comment
Oops, I forgot we have keras in host… well… |
Good point actually - afaik keras sits on top of tensorflow, so we might want to remove the keras host dep (at least to play around on this PR)? |
I usually wait until they tag something, https://github.com/tensorflow/tensorflow/tags. They usually do three RCs. It seems they're currently testing rc0 internally but haven't tagged it yet... |
Hm. Let's try! But that may be over the lite only. Let's see how this goes. some recs:
|
Time to switch to the prerelease and please feel free to include some of the other arches since we are interested in seeing how that plays out as well https://github.com/tensorflow/tensorflow/releases/tag/v2.12.0-rc0 |
…nda-forge-pinning 2023.02.16.23.42.32
This weird protobuf error now shows up everywhere - this commit introduced it: tensorflow/tensorflow@84f4092 |
I don't understand bazel, but this looks like it could be helpful: envoyproxy/envoy#23345 |
We are not supposed to be vendoring protobuf though, https://github.com/Tobias-Fischer/tensorflow-feedstock/blob/022daa6a1f2701be2426057b7e8395e771249f2c/recipe/build.sh#L43 I am sure @h-vetinari would be intrigued by this failure and the lovely commit upstream tensorflow/tensorflow@84f4092 |
we could try to vendor it to see if it gets us any further. Need to take it out from here https://github.com/Tobias-Fischer/tensorflow-feedstock/blob/022daa6a1f2701be2426057b7e8395e771249f2c/recipe/build.sh#L43 |
Feel free to play around here @ngam :) |
Any other places you've seen? Could you link them so that we can have a look? |
The current error is
which is definitely related to the commit you referenced tensorflow/tensorflow@84f4092. We can change that one piece since we rely on our own protobuf. Let me think |
Moved forward only very little:
Now hitting this: tensorflow/tensorflow#27697 |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
For recipe:
|
Same problem still in rc1:
|
Any objections to moving forward with #303 while some issues with 2.12 are resolved? |
No objections :) |
Let me know when everything is ready and I can potentially help build this week |
Go for it :) |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)