Skip to content
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

bash: line 2: syntax error near unexpected token `newline' #80

Closed
lukeyeager opened this issue Jan 7, 2016 · 6 comments
Closed

bash: line 2: syntax error near unexpected token `newline' #80

lukeyeager opened this issue Jan 7, 2016 · 6 comments

Comments

@lukeyeager
Copy link
Contributor

We're currently using the install-deps script for DIGITS TravisCI builds. It's started failing on me in the last two days with errors like this (but only intermittently?):

$ travis_wait ./scripts/travis/install-torch-wrapper.sh $(pwd)/deps/torch $(pwd)/torch-install-log.txt
Still running (1 of 20): ./scripts/travis/install-torch-wrapper.sh /home/travis/build/lukeyeager/DIGITS/deps/torch /home/travis/build/lukeyeager/DIGITS/torch-install-log.txt
The command ./scripts/travis/install-torch-wrapper.sh /home/travis/build/lukeyeager/DIGITS/deps/torch /home/travis/build/lukeyeager/DIGITS/torch-install-log.txt exited with 1.
Log:
+++'[' 2 -ne 2 ']'
+++INSTALL_DIR=/home/travis/build/lukeyeager/DIGITS/deps/torch
+++LOG_FILE=/home/travis/build/lukeyeager/DIGITS/torch-install-log.txt
+++./scripts/travis/install-torch.sh /home/travis/build/lukeyeager/DIGITS/deps/torch
+++cat /home/travis/build/lukeyeager/DIGITS/torch-install-log.txt
++++'[' 1 -ne 1 ']'
++++INSTALL_DIR=/home/travis/build/lukeyeager/DIGITS/deps/torch
++++mkdir -p /home/travis/build/lukeyeager/DIGITS/deps/torch
++++bash
++++curl -s https://raw.githubusercontent.com/torch/ezinstall/master/install-deps
bash: line 2: syntax error near unexpected token `newline'
bash: line 2: `<?xml version="1.0" encoding="utf-8"?>'
+++false
/home/travis/build.sh: line 112:  5605 Terminated              travis_jigger $! $timeout $cmd
The command "travis_wait ./scripts/travis/install-torch-wrapper.sh $(pwd)/deps/torch $(pwd)/torch-install-log.txt" failed and exited with 1 during .
Your build has been stopped.

https://travis-ci.org/lukeyeager/DIGITS/builds/100877937

Can we fix this, or do I need to figure out how to use a different Torch install mechanism? The README says the repo is deprecated, but according to this comment the install-deps script should still work:

The install-deps script is still in use, but the rest of the repo is indeed deprecated.
#79 (comment)

This could possibly be an issue on my end, totally unrelated to you. I'm looking into it...

@soumith
Copy link
Member

soumith commented Jan 7, 2016

luke, travis builds are famous for flaky network. It's possible that the install-deps script has been partially downloading occasionally. i've noticed the same in some of my contbuilds.

@soumith
Copy link
Member

soumith commented Jan 7, 2016

also, have you guys moved to the new travis cluster: https://docs.travis-ci.com/user/migrating-from-legacy/

@lukeyeager
Copy link
Contributor Author

Thanks for the quick response. I'll just keep restarting builds and hope that things settle down.

Are you talking about moving to trusty? I'd like to, but we depend on BVLC's Travis scripts to install Caffe on Travis and they're not very motivated to switch over from precise - BVLC/caffe#3407. Plus, I've tried to do it myself for Caffe and it's been pretty painful so far.

Have you moved to trusty with Torch? Or are you just talking about using their container/GCE architectures?

@soumith
Copy link
Member

soumith commented Jan 7, 2016

I'm talking about their container architectures. I've kept whatever is their default ubuntu install, didn't explicitly move to trusty

@lukeyeager
Copy link
Contributor Author

From what I've read, you need to turn off sudo to move to the docker-based container architecture (which we can't do), but you get upgraded to GCE automatically if you don't do anything - https://blog.travis-ci.com/2015-11-27-moving-to-a-more-elastic-future.

@soumith
Copy link
Member

soumith commented Jan 7, 2016

yea all it takes is to remove all sudo calls. The container architecture is soo nice, the builds are way faster and way less flakier.

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

No branches or pull requests

2 participants