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

travis_wait fail docker run #6934

Closed
galeksandrp opened this Issue Nov 25, 2016 · 3 comments

Comments

Projects
None yet
3 participants
@galeksandrp

galeksandrp commented Nov 25, 2016

$ travis_wait 120 docker run --rm -ti image bash -c "script.sh"


Still running (1 of 120): docker run --rm -ti image bash -c script.sh
The command docker run --rm -ti image bash -c script.sh exited with 1.

Log:

the input device is not a TTY
/home/travis/build.sh: line 151:  2198 Terminated              travis_jigger $! $timeout $cmd


The command "travis_wait 120 docker run --rm -ti image bash -c "script.sh"" exited with 1.

Done. Your build exited with 1.

https://travis-ci.org/galeksandrp/httpse/builds/178829025

Workaround is

travis_wait 120 sleep infinity &
docker run --rm -ti image bash -c "script.sh"

GitHub token from log has been regenerated.

@BanzaiMan

This comment has been minimized.

Member

BanzaiMan commented Nov 25, 2016

travis_wait works by checking the status of the process it sends to the background. If the process forks and execs another process, it doesn't work. I suspect this is the case with docker.

@torokati44

This comment has been minimized.

torokati44 commented Jan 31, 2018

I had the exact same problem. Your workaround worked well, thank you for it.

torokati44 added a commit to inet-framework/inet that referenced this issue Apr 9, 2018

torokati44 added a commit to inet-framework/inet that referenced this issue Apr 9, 2018

@stale

This comment has been minimized.

stale bot commented May 1, 2018

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment