Source: r10k Version: 2.2.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160707 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: with_setting(:proxy) { |value| > PuppetForge::V3::Base.conn.proxy(value) } > > #<Faraday::Connection:0x00000001b22040> received :proxy with > unexpected arguments > expected: ("http://my.site.proxy:3128") > got: (no args) > # ./lib/r10k/initializers.rb:52:in `block in call' > # ./lib/r10k/initializers.rb:22:in `with_setting' > # ./lib/r10k/initializers.rb:52:in `call' > # ./spec/unit/initializers_spec.rb:34:in `block (2 levels) in <top > (required)>' > > Finished in 2.77 seconds (files took 0.46484 seconds to load) > 590 examples, 1 failure, 1 pending > > Failed examples: > > rspec ./spec/unit/initializers_spec.rb:31 # > R10K::Initializers::ForgeInitializer configures PuppetForge connection proxy > > /usr/bin/ruby2.3 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb > --exclude-pattern ./spec/unit/forge/module_release_spec.rb failed > ERROR: Test "ruby2.3" failed: The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/07/r10k_2.2.0-1_unstable_reb.normal.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.