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

Suddenly failing Travis CI #180

Closed
pankajgupta opened this issue Apr 19, 2015 · 10 comments
Closed

Suddenly failing Travis CI #180

pankajgupta opened this issue Apr 19, 2015 · 10 comments

Comments

@pankajgupta
Copy link
Contributor

https://travis-ci.org/twitter/cassovary/builds shows that version with git tag 5.1.1 suddenly started failing travis ci builds, and every build since then has failed with the same message:
error sbt.ResolveException: unresolved dependency: com.twitter.common#metrics;0.0.29: not found

This is particularly strange since doing
$ git diff 5.1.0 5.1.1
shows no change.

Further, I created a branch called old-state-good-travis which goes back to the tip at 5.1.0 and it now also fails Travis build. https://travis-ci.org/twitter/cassovary/builds/59096320

I'm out of ideas -- @caniszczyk : any help when you get a chance would be really appreciated.

@pankajgupta
Copy link
Contributor Author

Created a new branch "new-travis-file" to play with different .travis.yml but doesn't seem to help. Throws the mysterious message while downloading metrics.jar. See https://travis-ci.org/twitter/cassovary/jobs/59100775
[warn] [FAILED ] com.twitter.common#metrics;0.0.29!metrics.jar: The HTTP response code for http://maven.twttr.com/com/twitter/common/metrics/0.0.29/metrics-0.0.29.jar did not indicate a success. See log for more detail. (1ms)

@pankajgupta
Copy link
Contributor Author

@travisbrown
Copy link
Contributor

Hi @pankajgupta, I've just sent you an email about this issue—it's an intermittent problem with the maven.twttr.com repository that needs more investigation.

@pankajgupta
Copy link
Contributor Author

Thanks for looking into it! I didn't seem to have gotten your email. Please
resend to pankaj@yogins.com

On Sunday, April 19, 2015, Travis Brown notifications@github.com wrote:

Hi @pankajgupta https://github.com/pankajgupta, I've just sent you an
email about this issue—it's an intermittent problem with the
maven.twttr.com repository that needs more investigation.


Reply to this email directly or view it on GitHub
#180 (comment).

@pankajgupta
Copy link
Contributor Author

@travisbrown any suggested fixes apart from just including that jar in repo.

@travisbrown
Copy link
Contributor

You can use - travis_retry sbt ++$TRAVIS_SCALA_VERSION test to make Travis retry the entire failed command three times—this has fixed the issue for us for other projects.

@caniszczyk
Copy link
Contributor

@pankajgupta checking through your dependencies, why do you need something from maven.twttr.com? Can we refactor something to remove the dependency? That should help with the flakiness and in the future, maven.twttr.com will eventually go away

@travisbrown
Copy link
Contributor

@caniszczyk At a glance it looks like it might not be too hard to remove the direct com.twitter.common dependencies here, but metrics is also needed by finagle-stats, which would be a lot harder to disentangle. We just need to start publishing this stuff to Maven Central.

@pankajgupta
Copy link
Contributor Author

That's right. Currently, we are using finagle-stats which needs metrics.

I am not sure if retries will help. Looks like very single travis build has
failed in the last few days.

What again is the intermittent problem with maven.twttr.com -- is it
unsolvable ?

On Mon, Apr 20, 2015 at 7:54 AM, Travis Brown notifications@github.com
wrote:

@caniszczyk https://github.com/caniszczyk At a glance it looks like it
might not be too hard to remove the direct com.twitter.common
dependencies here, but metrics is also needed by finagle-stats, which would
be a lot harder to disentangle. We just need to start publishing this stuff
to Maven Central.


Reply to this email directly or view it on GitHub
#180 (comment).

@pankajgupta
Copy link
Contributor Author

Solved for now by doing retries.

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

3 participants