8000 keep numpy version in pip.sh by jendap · Pull Request #1116 · tensorflow/tensorflow · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

keep numpy version in pip.sh #1116

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

Merged
merged 1 commit into from
Feb 16, 2016

Conversation

jendap
Copy link
Contributor
@jendap jendap commented Feb 16, 2016

We should keep building against numpy 1.8.2 - the version in ubuntu 14.04.

@jendap
8000
Copy link
Contributor Author
jendap commented Feb 16, 2016

Note: user home directory is cached between the builds - bazel is picking up the newer version installed after first run of pip.sh

Also this should be able to automatically downgrade all the installations in all the jobs on ci.tensorflow.org. But it will need two builds. First one will still pick the new version ob numpy.

@jendap
Copy link
Contributor Author
jendap commented Feb 16, 2016

Ok, it works. But the first build fails. Just like on this PR. The first bazel build took 1.10.4 cached from previous run and then failed while running test with downgraded 1.8.2. Next runs should work.

@tensorflow-jenkins: test this please

@jendap
Copy link
Contributor Author
jendap commented Feb 16, 2016

Also the docker container build with this works :-)

martinwicke added a commit that referenced this pull request Feb 16, 2016
@martinwicke martinwicke merged commit d0db73a into tensorflow:r0.7 Feb 16, 2016
@martinwicke
Copy link
Member

So we need to re-run the release twice to propagate this to the binaries?

@jendap jendap deleted the keep-numpy-version-in-pip.sh branch February 17, 2016 19:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0