-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Previous network clone epoch #1610
base: master
Are you sure you want to change the base?
Conversation
@@ -121,6 +121,7 @@ before_install: | |||
- deactivate | |||
- virtualenv --system-site-packages ~/venv | |||
- source ~/venv/bin/activate | |||
- sudo apt-get install libboost-filesystem1.55-dev libboost-python1.55-dev libboost-system1.55-dev libboost-thread1.55-dev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't these lines do the trick?
Lines 86 to 89 in 776131d
- libboost-filesystem-dev | |
- libboost-python-dev | |
- libboost-system-dev | |
- libboost-thread-dev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This build was fine, without the updated boost: https://travis-ci.org/NVIDIA/DIGITS/builds/217367405
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the change that broke things: BVLC/caffe#5526
|
||
# terrible hack to save the epoch for cloning |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is a "terrible hack" necessary?
When cloning a job using a previous network, the epoch is not saved in the job.