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

Trying to figure out why Travis will not approve #208 #212

Closed
wants to merge 7 commits into from

Conversation

edthedev
Copy link
Contributor

@edthedev edthedev commented May 3, 2016

Sorry for the spam. Want to see if I create a new pull from the same branch and commit if Travis CI will show the test passing.

The diff here looks identical to #208, to me; but #208 shows as not passing in Travis CI.
Yet when I wired Tavis CI to my fork and pushed a copy of the code in #208, the build passes.

Very odd.

@petegleeson
Copy link

Thanks for investigating this @edthedev. I agree, very strange behaviour with these CI builds. Seems ok now though.

@edthedev
Copy link
Contributor Author

edthedev commented May 3, 2016

Now that Travis CI passed here, I see that it has started passing in #208. Very odd. I will close this in favor of #208, since this pull seems to have served it's purpose: tricking the build on #208 to retry.

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