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

Spurious failure while installing deploy dependencies #44159

Closed
arielb1 opened this issue Aug 29, 2017 · 7 comments
Closed

Spurious failure while installing deploy dependencies #44159

arielb1 opened this issue Aug 29, 2017 · 7 comments
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@arielb1
Copy link
Contributor

arielb1 commented Aug 29, 2017

Found in #43938

�[0Ktravis_fold:end:dpl.0
�[0Ktravis_time:start:0914d468
�[0Ktravis_fold:start:dpl.1
�[33mInstalling deploy dependencies�[0m
ERROR:  Could not find a valid gem 'aws-sdk-core' (= 2.10.35) in any repository
ERROR:  Possible alternatives: aws-sdk-core
/home/travis/.rvm/rubies/ruby-2.2.7/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- aws-sdk (LoadError)
	from /home/travis/.rvm/rubies/ruby-2.2.7/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider.rb:85:in `requires'
	from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider/s3.rb:6:in `<class:S3>'
	from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider/s3.rb:5:in `<class:Provider>'
	from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider/s3.rb:4:in `<module:DPL>'
	from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider/s3.rb:3:in `<top (required)>'
	from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider.rb:59:in `const_get'
	from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider.rb:59:in `block in new'
	from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/cli.rb:41:in `fold'
	from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider.rb:56:in `new'
	from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/cli.rb:31:in `run'
	from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/cli.rb:7:in `run'
	from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/bin/dpl:5:in `<top (required)>'
	from /home/travis/.rvm/gems/ruby-2.2.7/bin/dpl:22:in `load'
	from /home/travis/.rvm/gems/ruby-2.2.7/bin/dpl:22:in `<main>'

travis_fold:end:dpl.1
failed to deploy
@arielb1 arielb1 added the A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) label Aug 29, 2017
@kennytm
Copy link
Member

kennytm commented Aug 29, 2017

The error means the gem repository is not up-to-date, and a retry will usually fix it. This happened at least twice before:

Maybe we could do something like gem update before deploying to S3.

@shepmaster shepmaster added C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Sep 1, 2017
kennytm added a commit to kennytm/rust that referenced this issue Nov 5, 2017
kennytm added a commit to kennytm/rust that referenced this issue Nov 10, 2017
…crichton

Miscellaneous changes for CI, Docker and compiletest.

This PR contains 7 independent commits that improves interaction with CI, Docker and compiletest.

1. a4e5c91 — Forces a newline every 100 dots when testing in quiet mode. Prevents spurious timeouts when abusing the CI to test Android jobs.

2. 1b5aaf2 — Use vault.centos.org for dist-powerpc64le-linux, see rust-lang#45744.

3. 33400fb — Modify `src/ci/docker/run.sh` so that the docker images can be run from Docker Toolbox for Windows on Windows 7. I haven't checked the behavior of the newer Docker for Windows on Windows 10. Also, "can run" does not mean all the test can pass successfully (the UDP tests failed last time I checked)

4. d517668 — Don't emit a real warning the linker segfault, which affects UI tests like rust-lang#45489 (comment). Log it instead.

5. 51e2247 — During run-pass, trim the output if stdout/stderr exceeds 416 KB (top 160 KB + bottom 256 KB). This is an attempt to avoid spurious failures like rust-lang#45384 (comment)

6. 9cfdaba — Force `gem update --system` before deploy. This is an attempt to prevent spurious error rust-lang#44159.

7. eee10cc — Tries to print the crash log on macOS on failure. This is an attempt to debug rust-lang#45230.
@kennytm
Copy link
Member

kennytm commented Nov 22, 2017

The attempt to fix this at 9cfdaba does not work, it still cannot install an updated gem.

@kennytm
Copy link
Member

kennytm commented Dec 5, 2017

Update: We haven't got any simple solutions for this yet https://mozilla.logbot.info/rust-infra/20171205#c13967953-c13968089.

@kennytm
Copy link
Member

kennytm commented Dec 6, 2017

The most recent error has an upstream issue at travis-ci/travis-ci#8862, which was caused by Travis's deployment software dpl not pinning the AWS SDK version (travis-ci/dpl#718). Additionally AWS has some questionable release strategy which publishes a gem without publishing a new required dependency first (aws/aws-sdk-ruby#1667), causing the problem we see here.

An attempt to fix this on upstream can be found at travis-ci/dpl#724. If that (or similar PRs) has been merged, and we no longer see this spurious failure happening for 4 weeks, we could close this issue.

@alexcrichton
Copy link
Member

Today's failure does seem to coincide with a release of the dpl gem (March 12, 2018). As to what that means, no idea!

@pietroalbini
Copy link
Member

Seems like Travis failed to fetch some ruby dependencies again? #50937 (comment)

@alexcrichton
Copy link
Member

With #55304 this should hopefully no longer happen as we're not using Travis's built-in deployment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

5 participants