Source: ruby-gh
Version: 0.18.0-4
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: [email protected]
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-gh failed to build.

Relevant part of the build log (hopefully):
>      Failure/Error: expect { subject['/x'] }.to 
> raise_error(GH::Error(:response_status => 500))
> 
>        expected #<Module:0x00007fc649c453f8>, got 
> #<RSpec::Mocks::MockExpectationError: #<GH::Remote: https://api.github.com> 
> received :http with unexp...ken", {"Authorization"=>"Basic Zm9vOmJhcg==", 
> :body=>"{\"access_token\": \"baz\"}"}) (options hash)> with backtrace:
>          # ./lib/gh/token_check.rb:28:in `http'
>          # ./lib/gh/token_check.rb:21:in `check_token'
>          # ./lib/gh/token_check.rb:27:in `http'
>          # ./lib/gh/remote.rb:66:in `fetch_resource'
>          # ./lib/gh/wrapper.rb:82:in `[]'
>          # ./spec/token_check_spec.rb:25:in `block (3 levels) in <top 
> (required)>'
>          # ./spec/token_check_spec.rb:25:in `block (2 levels) in <top 
> (required)>'
>      # ./spec/token_check_spec.rb:25:in `block (2 levels) in <top (required)>'
> 
> Deprecation Warnings:
> 
> Using `should_receive` 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/custom_limit_spec.rb:17:in `block (2 levels) in <top 
> (required)>'.
> 
> 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/cache_spec.rb:7: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 1 second (files took 0.46356 seconds to load)
> 115 examples, 2 failures, 9 pending
> 
> Failed examples:
> 
> rspec ./spec/token_check_spec.rb:10 # GH::TokenCheck adds client_id and 
> client_secret to a request
> rspec ./spec/token_check_spec.rb:19 # GH::TokenCheck does not swallow other 
> status codes
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is attached.

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

Attachment: ruby-gh.log.gz
Description: application/gzip

Attachment: signature.asc
Description: PGP signature

Reply via email to