Source: ruby-gemnasium-gitlab-service Version: 0.2.6-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Failure/Error: @connection.request(request) > > WebMock::NetConnectNotAllowedError: > Real HTTP connections are disabled. Unregistered request: POST > https://api.gemnasium.com/v1/test_path with body '{"foo":"bar"}' with headers > {'Accept'=>'application/json', > 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', > 'Authorization'=>'Basic WDpzZWNyZXRfYXBpX2tleQ==', > 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - > v0.2.6'} > > You can stub this request with the following snippet: > > stub_request(:post, "https://api.gemnasium.com/v1/test_path"). > with(body: "{\"foo\":\"bar\"}", > headers: {'Accept'=>'application/json', > 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', > 'Authorization'=>'Basic WDpzZWNyZXRfYXBpX2tleQ==', > 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - > v0.2.6'}). > to_return(status: 200, body: "", headers: {}) > > registered request stubs: > > stub_request(:post, > "https://X:secret_api_...@api.gemnasium.com/v1/test_path"). > with(body: {"foo"=>"bar"}, > headers: {'Accept'=>'application/json', > 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - > v0.2.6'}) > stub_request(:get, > "https://X:secret_api_...@api.gemnasium.com/v1/test_path"). > with(headers: {'Accept'=>'application/json', > 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - > v0.2.6'}) > stub_request(:post, > "https://X:secret_api_...@api.gemnasium.com/v1/projects/project_slug/dependency_files"). > with(headers: {'Accept'=>'application/json', > 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - > v0.2.6'}) > > ============================================================ > # ./lib/gemnasium/gitlab_service/connection.rb:28:in `post' > # ./spec/gemnasium/gitlab_service/connection_spec.rb:25:in `block (3 > levels) in <top (required)>' > > Deprecation Warnings: > > Using `should` from rspec-expectations' old `:should` syntax without > explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or > explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = > :should }` instead. Called from > /<<PKGBUILDDIR>>/spec/gemnasium/gitlab_service/client_spec.rb:11:in `block (3 > levels) in <top (required)>'. > > Using `stub` from rspec-mocks' old `:should` syntax without explicitly > enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly > enable `:should` instead. Called from > /<<PKGBUILDDIR>>/spec/gemnasium/gitlab_service/pusher_spec.rb:8:in `block (2 > levels) in <top (required)>'. > > > If you need more of the backtrace for any of these deprecations to > identify where to make the necessary changes, you can configure > `config.raise_errors_for_deprecations!`, and it will turn the > deprecation warnings into errors, giving you the full backtrace. > > 2 deprecation warnings total > > Finished in 0.02929 seconds (files took 0.65037 seconds to load) > 8 examples, 3 failures > > Failed examples: > > rspec ./spec/gemnasium/gitlab_service/client_spec.rb:30 # > Gemnasium::GitlabService::Client upload_files issues a POST request > rspec ./spec/gemnasium/gitlab_service/connection_spec.rb:18 # > Gemnasium::GitlabService::Connection get issues a GET request > rspec ./spec/gemnasium/gitlab_service/connection_spec.rb:27 # > Gemnasium::GitlabService::Connection post issues a POST request > > /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format > documentation failed > ERROR: Test "ruby2.3" failed: The full build log is available from: http://aws-logs.debian.net/2017/07/07/ruby-gemnasium-gitlab-service_0.2.6-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.