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

Fix Travis build failure #787

Merged
merged 1 commit into from
Jul 20, 2016
Merged

Fix Travis build failure #787

merged 1 commit into from
Jul 20, 2016

Conversation

afestein
Copy link

@afestein afestein commented Jul 18, 2016

When RubyMotion is updated during the Travis build, the update command
returns an exit code of 1 if the software is already up to date.
According to the Travis
documentation
,
a non-zero exit code will cause the build to fail.

See https://travis-ci.org/infinitered/ProMotion/builds/145458532 for an
example of a failing build.

Catching this non-error lets us continue with the build.

When RubyMotion is updated during the Travis build, the update command
returns an exit code of 1 if the software is already up to date.
According to the [Travis
documentation](https://docs.travis-ci.com/user/customizing-the-build/),
a non-zero exit code will cause the build to fail.

See https://travis-ci.org/infinitered/ProMotion/builds/145458532 for an
example of a failing build.

Catching this non-error lets us continue with the build.
@andrewhavens
Copy link
Collaborator

motion update returns a non-zero exit code when it is already up to date? 🤦

Thanks for fixing this. 👍

@andrewhavens andrewhavens merged commit 133aaaa into jamonholmgren:master Jul 20, 2016
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

Successfully merging this pull request may close these issues.

2 participants