Your message dated Thu, 16 Mar 2023 05:56:29 +0000
with message-id <e1pcgbf-009iyd...@fasolo.debian.org>
and subject line Bug#1032693: Removed package(s) from unstable
has caused the Debian Bug report #1026491,
regarding puppet-beaker: FTBFS: [31mFailure/Error: [0mhosts_yaml =
[1;34;4mYAML[0m.load_file(preserved_file)[0m
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: puppet-beaker
Version: 4.30.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> rspec
>
> Beaker::CLI
> initializing and parsing
> instance variable initialization
> [32m creates a logger for use before parse is called[0m
> [32m generates the timestamp[0m
> #parse_options
> [32m returns self[0m
> [32m replaces the logger object with a new one[0m
> #parse_options special behavior
> [32m prints the version and exits cleanly[0m
> [32m prints the help and exits cleanly[0m
> #print_version_and_options
> [32m prints the version and dumps the options[0m
> #configured_options
> [32m returns a list of options that were not presets[0m
> #combined_instance_and_options_hosts
> [32m combines the options and instance host objects[0m
> when hosts share IP addresses
> [32m creates separate entries for each host[0m
> execute!
> test fail mode
>
> WARNING: Using the `raise_error` matcher without providing a specific error
> or message risks false positives, since `raise_error` will match when Ruby
> raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially
> allowing the expectation to pass without even executing the method you are
> intending to call. Actual error raised was #<SystemExit: exit>. Instead
> consider providing a specific error class or message. This message can be
> suppressed by setting:
> `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`.
> Called from /<<PKGBUILDDIR>>/spec/beaker/cli_spec.rb:152:in `block (4 levels)
> in <module:Beaker>'.
> [32m runs pre_cleanup after a failed pre_suite if using slow
> fail_mode[0m
>
> WARNING: Using the `raise_error` matcher without providing a specific error
> or message risks false positives, since `raise_error` will match when Ruby
> raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially
> allowing the expectation to pass without even executing the method you are
> intending to call. Actual error raised was #<SystemExit: exit>. Instead
> consider providing a specific error class or message. This message can be
> suppressed by setting:
> `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`.
> Called from /<<PKGBUILDDIR>>/spec/beaker/cli_spec.rb:169:in `block (4 levels)
> in <module:Beaker>'.
> [32m continues testing after failed test if using slow fail_mode[0m
>
> WARNING: Using the `raise_error` matcher without providing a specific error
> or message risks false positives, since `raise_error` will match when Ruby
> raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially
> allowing the expectation to pass without even executing the method you are
> intending to call. Actual error raised was #<SystemExit: exit>. Instead
> consider providing a specific error class or message. This message can be
> suppressed by setting:
> `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`.
> Called from /<<PKGBUILDDIR>>/spec/beaker/cli_spec.rb:182:in `block (4 levels)
> in <module:Beaker>'.
> [32m stops testing after failed test if using fast fail_mode[0m
> SUT preserve mode
>
> WARNING: Using the `raise_error` matcher without providing a specific error
> or message risks false positives, since `raise_error` will match when Ruby
> raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially
> allowing the expectation to pass without even executing the method you are
> intending to call. Actual error raised was #<SystemExit: exit>. Instead
> consider providing a specific error class or message. This message can be
> suppressed by setting:
> `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`.
> Called from /<<PKGBUILDDIR>>/spec/beaker/cli_spec.rb:201:in `block (4 levels)
> in <module:Beaker>'.
> [32m cleans up SUTs post testing if tests fail and preserve_hosts =
> never[0m
> [32m cleans up SUTs post testing if no tests fail and preserve_hosts =
> never[0m
> [32m preserves SUTs post testing if no tests fail and preserve_hosts =
> always[0m
> WARNING: Using the `raise_error` matcher without providing a specific error
> or message risks false positives, since `raise_error` will match when Ruby
> raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially
> allowing the expectation to pass without even executing the method you are
> intending to call. Actual error raised was #<TypeError: no implicit
> conversion of nil into String>. Instead consider providing a specific error
> class or message. This message can be suppressed by setting:
> `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`.
> Called from /<<PKGBUILDDIR>>/spec/beaker/cli_spec.rb:259:in `block (4 levels)
> in <module:Beaker>'.
> [32m preserves SUTs post testing if no tests fail and preserve_hosts =
> always[0m
> [32m cleans up SUTs post testing if no tests fail and preserve_hosts =
> onfail[0m
> WARNING: Using the `raise_error` matcher without providing a specific error
> or message risks false positives, since `raise_error` will match when Ruby
> raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially
> allowing the expectation to pass without even executing the method you are
> intending to call. Actual error raised was #<TypeError: no implicit
> conversion of nil into String>. Instead consider providing a specific error
> class or message. This message can be suppressed by setting:
> `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`.
> Called from /<<PKGBUILDDIR>>/spec/beaker/cli_spec.rb:294:in `block (4 levels)
> in <module:Beaker>'.
> [32m preserves SUTs post testing if tests fail and preserve_hosts =
> onfail[0m
>
> WARNING: Using the `raise_error` matcher without providing a specific error
> or message risks false positives, since `raise_error` will match when Ruby
> raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially
> allowing the expectation to pass without even executing the method you are
> intending to call. Actual error raised was #<SystemExit: exit>. Instead
> consider providing a specific error class or message. This message can be
> suppressed by setting:
> `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`.
> Called from /<<PKGBUILDDIR>>/spec/beaker/cli_spec.rb:312:in `block (4 levels)
> in <module:Beaker>'.
> [32m cleans up SUTs post testing if tests fail and preserve_hosts =
> onpass[0m
> [32m preserves SUTs post testing if no tests fail and preserve_hosts =
> onpass[0m
> #preserve_hosts_file
> [31m removes the pre-suite/post-suite/tests and sets to [] (FAILED -
> 1)[0m
>
> Failures:
>
> 1) Beaker::CLI execute! #preserve_hosts_file removes the
> pre-suite/post-suite/tests and sets to []
> [31mFailure/Error: [0mhosts_yaml =
> [1;34;4mYAML[0m.load_file(preserved_file)[0m
> [31m[0m
> [31mPsych::DisallowedClass:[0m
> [31m Tried to load unspecified class: Beaker::Options::OptionsHash[0m
> [36m# ./spec/beaker/cli_spec.rb:364:in `block (4 levels) in
> <module:Beaker>'[0m
>
> Finished in 0.21811 seconds (files took 1.27 seconds to load)
> [31m22 examples, 1 failure[0m
>
> Failed examples:
>
> [31mrspec ./spec/beaker/cli_spec.rb:338[0m [36m# Beaker::CLI execute!
> #preserve_hosts_file removes the pre-suite/post-suite/tests and sets to [][0m
>
> make[1]: *** [debian/rules:10: override_dh_auto_test] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/12/20/puppet-beaker_4.30.0-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
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!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 4.30.0-2+rm
Dear submitter,
as the package puppet-beaker has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1032693
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
