Initial commit of python-tensorflow-serving-api
Details
Details
- Reviewers
JoshStrobl - Group Reviewers
Triage Team - Commits
- R4695:8aff44a58785: Initial commit of python-tensorflow-serving-api
Dependency of D5202
Diff Detail
Diff Detail
- Repository
- R4695 python-tensorflow-serving-api
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
@xulongwu4 Issue during build:
+ bazel build //tensorflow_serving/tools/pip_package:build_pip_package WARNING: The following rc files are no longer being read, please transfer their contents or import their path into one of the standard rc files: /home/build/YPKG/root/python-tensorflow-serving-api/build/serving-1.12.0/tools/bazel.rc file is invalid or corrupted (missing end of central directory record) Cannot find central directory FATAL: Failed to open Bazel as a zip file: (error: 5): Input/output error
This comment was removed by xulongwu4.
Comment Actions
@JoshStrobl This error is caused by broken bazel build (see T7193). Even though the bazel build according to D5204 worked on my machine, the binary produced by the build server seems not to work. I am not clear at the moment what can cause the issue.
Comment Actions
@JoshStrobl
One peculiar thing to notice is that the binary provided by the server only has a size of 0.57 M while I built it on my machine and got a binary of 107 M. This definitely indicates differences in these binaries.
Comment Actions
So more research shows that this is caused by stripping the bazel binary during build. And when I stripped the 107 M binary, I got a binary of 0.5 M. Thus it is reasonable to assume that stripping happened during the build on the server.
@JoshStrobl If you look at package.yml for D5204, I did set strip: no there. I am not 100% sure, but I suspect the we are still stripping for the debug symbols (because I see we have the bazel-dbginfo package). I am wondering if we can disable the production of a dbginfo package of bazel on the server and see if that fixes the issue.