Skip to content
This repository has been archived by the owner on Mar 25, 2020. It is now read-only.

why pending at the time cloning tensorboard-lite? #57

Open
Davidrjx opened this issue Feb 12, 2018 · 3 comments
Open

why pending at the time cloning tensorboard-lite? #57

Davidrjx opened this issue Feb 12, 2018 · 3 comments

Comments

@Davidrjx
Copy link

Davidrjx commented Feb 12, 2018

@zihaolucky ,running sh installer.sh keeps pending, i do not know whether it is normal, like

protoc tensorboard/src/*.proto --python_out=python/
Submodule 'tensorboard-lite' (https://github.com/zihaolucky/tensorboard-lite.git) registered for path 'tensorboard-lite/tensorboard-lite'
Cloning into '$HOME/tensorboard/tensorboard-lite'...
@Davidrjx
Copy link
Author

Davidrjx commented Feb 12, 2018

@zihaolucky problem above has been resolved but came with a new error find: ‘/usr/include/python2.7’: No such file or directory , while i use system python2.7.13 in virtualenv.

@zihaolucky
Copy link
Member

tensorboard-lite is a submodule we need. Could you provide more log for the coming problem?

@Davidrjx
Copy link
Author

@zihaolucky
above problem has been ok, but when i run sh installer.sh , came with the following error

ERROR: /opt/tensorboard/tensorboard-lite/tensorboard/java/org/tensorflow/tensorboard/vulcanize/BUILD:25:1: Creating runfiles tree bazel-out/host/bin/tensorboard/java/org/tensorflow/tensorboard/vulcanize/Zipper.runfiles [for host] failed (Exit 1)
_bin/build-runfiles (args bazel-out/host/bin/tensorboard/java/org/tensorflow/tensorboard/vulcanize/Zipper.runfiles_manifest bazel-out/host/bin/tensorboard/java/org/tensorflow/tensorboard/vulcanize/Zipper.runfiles): link or target filename contains space on line 3987: 'local_jdk/lib/python3.6/site-packages/setuptools/command/launcher manifest.xml /root/.cache/bazel/_bazel_root/96c18647ee71fa3ee56fa5b9f43eac30/external/local_jdk/lib/python3.6/site-packages/setuptools/command/launcher manifest.xml'

Target //tensorboard:tensorboard failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 11.041s, Critical Path: 9.68s
FAILED: Build did NOT complete successfully

can you please help me analyze this issue?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants