[DRE-maint] Bug#835693: ruby-oauth2: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect { subject.header('get', 'this-is-not-valid') }.to raise_error(ArgumentError)

Lucas Nussbaum lucas at debian.org
Sun Aug 28 10:31:57 UTC 2016


Source: ruby-oauth2
Version: 1.2.0-1
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20160828 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: expect { subject.header('get', 'this-is-not-valid') }.to raise_error(ArgumentError)
> 
>        expected ArgumentError, got #<NameError: uninitialized constant URI::RFC3986_Parser::Generic> with backtrace:
>          # ./lib/oauth2/mac_token.rb:65:in `header'
>          # ./spec/oauth2/mac_token_spec.rb:69:in `block (4 levels) in <top (required)>'
>          # ./spec/oauth2/mac_token_spec.rb:69:in `block (3 levels) in <top (required)>'
>      # ./spec/oauth2/mac_token_spec.rb:69:in `block (3 levels) in <top (required)>'
> 
> Finished in 0.18965 seconds (files took 0.25918 seconds to load)
> 185 examples, 4 failures
> 
> Failed examples:
> 
> rspec ./spec/oauth2/mac_token_spec.rb:78 # OAuth2::MACToken#signature generates properly
> rspec ./spec/oauth2/mac_token_spec.rb:56 # OAuth2::MACToken#header does not generate the same header twice
> rspec ./spec/oauth2/mac_token_spec.rb:63 # OAuth2::MACToken#header generates the proper format
> rspec ./spec/oauth2/mac_token_spec.rb:68 # OAuth2::MACToken#header passes ArgumentError with an invalid url
> 
> Randomized with seed 43994
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/ruby-oauth2_1.2.0-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.



More information about the Pkg-ruby-extras-maintainers mailing list