[tensorflow-cc] Update to 2.10.0#24861
Conversation
5aaf4d2 to
eae9113
Compare
There was a problem hiding this comment.
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/tensorflow-cc/vcpkg.jsonports/tensorflow-common/vcpkg.jsonports/tensorflow/vcpkg.json
Valid values for the license field can be found in the documentation
There was a problem hiding this comment.
You have modified or added at least one vcpkg.json where you should check the license field.
Details
If you feel able to do so, please consider adding a "license" field to the following files:
ports/tensorflow-cc/vcpkg.jsonports/tensorflow-common/vcpkg.jsonports/tensorflow/vcpkg.json
Valid values for the license field can be found in the documentation
eae9113 to
83a8121
Compare
83a8121 to
49f294a
Compare
49f294a to
7ab0dc4
Compare
|
Thanks for the PR! Can we be more surgical about these removals? What are they specifically removing? We should be redirecting all bazel files to stay within the vcpkg instance. |
|
Hello @ras0219-msft,
This is where my pipeline failed : https://dev.azure.com/vcpkg/public/_build/results?buildId=72552&view=logs&j=f79cfdd7-47a8-597f-8f57-dc3e21a8f2ad. Firstly, the Then in the Seems like it's an error raised from IMHO, it's a better idea to cleanup those working directory, so we can get a fresh work space everytime when we trigger the workflow. |
|
Hello @ras0219-msft , |
|
@ras0219-msft ,Could you please take a review? |
|
2.9.0 is out now. |
|
@JackyYin ,Could you please update tensorflow-cc to the lateste version 2.9.0? |
|
By the way, is it correct that tensor-flow is not supported on arm? |
It's my pleasure, I will update this patch as soon as possible. |
7ab0dc4 to
e11d674
Compare
|
@JackyYin TensorFlow 2.10 has been released, could you try updating this PR? |
41ff788
8555098 to
41ff788
Compare
There was a problem hiding this comment.
This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!
PRs must add only one version and must not modify any published versions
When making any changes to a library, the version or port-version in vcpkg.json or CONTROL must be modified.
error: checked-in files for tensorflow-common have changed but the version was not updated
version: 2.10.0
old SHA: 44ba099d1b61759bd520a48486e2b88fef616397
new SHA: 86fd281d0d4da2f16538f684741e3fa07cc98406
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***
41ff788 to
e168873
Compare
|
Hi @JonLiu1993 , |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
e168873 to
81c45c2
Compare
…orflow-cc-2.8.0
|
build failure on Windows x64 -- Configuring TensorFlow (dbg) Call Stack (most recent call first): |
Update
tensorflow-ccto 2.10.0.Bacause
tensorflow-ccdepends ontensorflow-commonandtensorflowdepends ontensorflow-commontoo, so I update all of these package to 2.10.0 at once.Also added a new host port
vcpkg-tool-bazelas a dependency oftensorflowandtensorflow-cc, bacause tensorflow 2.10.0 requires newer version of bazel.Tested triplet:
x64-osx
x64-linux
arm64-osx