Source: ruby-puppet-syntax Version: 2.6.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Failure/Error: expect(output.size).to eq(0) > > expected: 0 > got: 1 > > (compared using ==) > # ./spec/puppet-syntax/manifests_spec.rb:165:in `block (4 levels) in > <top (required)>' > > 2) PuppetSyntax::Templates on Puppet >= 3.7 should return nothing from a > valid file FIXED > Expected pending 'puppet is causing a ruby warning and fails the purpose > of this test' to fail. No error was raised. > # ./spec/puppet-syntax/templates_spec.rb:99 > > 3) PuppetSyntax::Templates on Puppet >= 3.7 should catch SyntaxError FIXED > Expected pending 'puppet is causing a ruby warning and fails the purpose > of this test' to fail. No error was raised. > # ./spec/puppet-syntax/templates_spec.rb:107 > > 4) PuppetSyntax::Templates on Puppet >= 3.7 should read more than one valid > file FIXED > Expected pending 'puppet is causing a ruby warning and fails the purpose > of this test' to fail. No error was raised. > # ./spec/puppet-syntax/templates_spec.rb:116 > > 5) PuppetSyntax::Templates on Puppet >= 3.7 should continue after finding > an error in the first file FIXED > Expected pending 'puppet is causing a ruby warning and fails the purpose > of this test' to fail. No error was raised. > # ./spec/puppet-syntax/templates_spec.rb:124 > > 6) PuppetSyntax::Templates on Puppet >= 3.7 when the 'epp_only' options is > set should process an ERB as EPP and find an error FIXED > Expected pending 'puppet is causing a ruby warning and fails the purpose > of this test' to fail. No error was raised. > # ./spec/puppet-syntax/templates_spec.rb:139 > > Finished in 0.12527 seconds (files took 0.75656 seconds to load) > 43 examples, 6 failures > > Failed examples: > > rspec ./spec/puppet-syntax/manifests_spec.rb:159 # PuppetSyntax::Manifests > app_management app_management = true should successfully parse an application > manifest on Puppet >= 4.3.0 > rspec ./spec/puppet-syntax/templates_spec.rb:99 # PuppetSyntax::Templates on > Puppet >= 3.7 should return nothing from a valid file > rspec ./spec/puppet-syntax/templates_spec.rb:107 # PuppetSyntax::Templates on > Puppet >= 3.7 should catch SyntaxError > rspec ./spec/puppet-syntax/templates_spec.rb:116 # PuppetSyntax::Templates on > Puppet >= 3.7 should read more than one valid file > rspec ./spec/puppet-syntax/templates_spec.rb:124 # PuppetSyntax::Templates on > Puppet >= 3.7 should continue after finding an error in the first file > rspec ./spec/puppet-syntax/templates_spec.rb:139 # PuppetSyntax::Templates on > Puppet >= 3.7 when the 'epp_only' options is set should process an ERB as EPP > and find an error > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/09/26/ruby-puppet-syntax_2.6.1-2_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.
