[DRE-maint] Bug#959624: ruby-faraday: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `split' for nil:NilClass

[Lucas Nussbaum]

Source: ruby-faraday
Version: 0.15.4-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> NoMethodError: undefined method `split' for nil:NilClass
>     /usr/lib/ruby/vendor_ruby/rack/mock.rb:236:in `identify_cookie_attributes'
>     /usr/lib/ruby/vendor_ruby/rack/mock.rb:220:in `block in parse_cookies_from_header'
>     /usr/lib/ruby/vendor_ruby/rack/mock.rb:218:in `each'
>     /usr/lib/ruby/vendor_ruby/rack/mock.rb:218:in `parse_cookies_from_header'
>     /usr/lib/ruby/vendor_ruby/rack/mock.rb:169:in `initialize'
>     /usr/lib/ruby/vendor_ruby/rack/mock_session.rb:32:in `new'
>     /usr/lib/ruby/vendor_ruby/rack/mock_session.rb:32:in `request'
>     /usr/lib/ruby/vendor_ruby/rack/test.rb:249:in `process_request'
>     /usr/lib/ruby/vendor_ruby/rack/test.rb:125:in `request'
>     /<<PKGBUILDDIR>>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/adapter/rack.rb:54:in `execute_request'
>     /<<PKGBUILDDIR>>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/adapter/rack.rb:46:in `call'
>     /<<PKGBUILDDIR>>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/response.rb:8:in `call'
>     /<<PKGBUILDDIR>>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/request/url_encoded.rb:15:in `call'
>     /<<PKGBUILDDIR>>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/request/multipart.rb:15:in `call'
>     /<<PKGBUILDDIR>>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/rack_builder.rb:143:in `build_response'
>     /<<PKGBUILDDIR>>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/connection.rb:387:in `run_request'
>     /<<PKGBUILDDIR>>/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/connection.rb:138:in `get'
>     /usr/lib/ruby/2.7.0/forwardable.rb:235:in `get'
>     /<<PKGBUILDDIR>>/test/adapters/integration.rb:98:in `test_GET_handles_headers_with_multiple_values'
>     /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run'
>     /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions'
>     /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it'
>     /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
>     /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler'
>     /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun'
> 
> 265 runs, 414 assertions, 0 failures, 1 errors, 6 skips
> 
> You have skipped tests. Run with --verbose for details.
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/ruby-faraday_0.15.4-3_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.