-
-
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
tensorflow 2.11 #286
tensorflow 2.11 #286
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 2022.11.20.19.10.04
…nda-forge-pinning 2022.11.22.12.08.38
macos runs failing with "snappy.h not found", likely related to this commit: tensorflow/tensorflow@05ad750 Fixed locally, update PR 7f20e5a. Test failures on linux-64 cpu builds: (fixed in 7f20e5a)
xref: Likely, this line needs to be changed to reflect new changes (Eigen --> Eigen & tsl?): https://github.com/ngam/tensorflow-feedstock/blob/4c529f97eacc3f8e185c1376865fe9c21b022e27/recipe/build.sh#LL188 fixed! |
@xhochy how can I build tensorflow osx-arm64 natively on M1 using this recipe? It is cross-compiled as is, and I cannot remember what changes you made that made it cross-compile (it used to be native). Wildly enough, for now this recipe can only compile for osx-arm64 if I am inside a conda osx-64 env, to then cross-compile for osx-arm64. Even crazier, it completely fails for osx-64. It always fails if I start from an osx-arm64 env. The errors I get are somewhat incoherent, except for the case when starting with osx-arm64 env to compile osx-64 (it complains about x86_64 stuff) |
I cannot build the osx ones (something is wrong with my local setup). Others are welcome to try. Sorry. |
can you build anything from osx? maybe even x86? |
No, for some reason, I cannot build anything. It is surprising because it is failing much earlier than the CI... However, my machines are arm64, so I assume that might be it... |
If nobody attempts to build, I will have another closer look next week. There also seems to be some effort to change how they build osx (especially to open-source Metal plug). I will also update this to include openssl3 before we merge. |
Should we attempt to migrate libgrpc 1.50 in the meantime (I could do it)? 1.51 is already out (we could even migrate to that1), and tensorflow is one of the trickiest ones to get on even footing w.r.t. grpc, making it hard to install with other packages. Footnotes
|
Yes, we can tinker around. Also please know that I can readily and quickly build the linux stuff at least through the end of Dec (I will lose access to a lot of computing resources on Dec 31 😢) |
Grpc PR arrived: #289 Should be easy to include. :) Pity to hear you'll lose access to those compute resources, it was very helpful to have you building/debugging things so regularly |
Fingers crossed I will have access to even better systems (maybe even including some of these alt linux arches we struggle with...) 😉 (It will just take a bit of time to get everything set up... so hopefully not more than ~60-day interruption!) |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2022.12.08.16.56.34
Will attempt building this again over the weekend |
So flatbuffers 22 was released yesterday on conda-forge breaking the so name. |
My anaconda account I never got the cross-builds to pass the testing phase due to cross-execution issues but that doesn't mean that there's anything wrong with the builds. (I think I must be doing something wrong with setting up the cross build invocation ... my last error was with the |
the build locally command should skip the tests right? Sorry i just got back from travels, i'll move the builds over. |
I've tested python 3.9 and cuda, as well as CPU on linux using my workflow. seems to work ok. i'm going to upload all. Thanks for the hard work. I seemed to have a problem with openssl3+cuda on linux though. I can't seem to point it down. |
In order to build the subpackages that have Python dependencies, they need to have Python and cross-python as build deps. tensorflow-estimator further needs to have tensorflow-base as a build dep because its build process needs to `import tensorflow` in order to generate API bindings, and in the cross-python setup the build-arch package is required to provide binary Python modules for import.
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:
|
Ok, all got uploaded. Thanks all. Onto the next stuff. Seems like grpc 1.51 also got folded in. |
Woohoo, thanks everyone for all the hard work! 🥳
Yes, that was explicitly a goal. |
It really became hard to follow what got "done" especially since the migration file got deleted. Ultimately, i checked a few logs. |
That's because the migration got closed in the meantime (it was clear that the next TF build would contain it), and it's right there in the diff (for the config yamls). But happy to answer any questions about these things next time. |
i think what might help as these CFEP03 builds get done is if somebody wanted to keep the top level comment updated with highlights such as this one. Thanks for help on all of these difficult builds! |
Thanks all, especially @pkgw and as always @hmaarrfk and @h-vetinari for keeping track of everything. Hopefully things are going to be easier in the next releases. Thanks!!! |
Included migrations
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)