Skip to content

keep numpy version in pip.sh#1116

Merged
martinwicke merged 1 commit into
tensorflow:r0.7from
jendap:keep-numpy-version-in-pip.sh
Feb 16, 2016
Merged

keep numpy version in pip.sh#1116
martinwicke merged 1 commit into
tensorflow:r0.7from
jendap:keep-numpy-version-in-pip.sh

Conversation

@jendap
Copy link
Copy Markdown
Contributor

@jendap jendap commented Feb 16, 2016

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

@jendap
Copy link
Copy Markdown
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
Copy Markdown
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
Copy Markdown
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
Copy Markdown
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