Your message dated Sat, 24 Dec 2022 14:19:22 +0530
with message-id <20221224084922.pe6bwmfwzqlho...@nileshpatra.info>
and subject line Re: ruby-excon: FTBFS with ruby3.1: ERROR: Test "ruby3.1"
failed: RuntimeError:
has caused the Debian Bug report #1019621,
regarding ruby-excon: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
RuntimeError:
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.)
--
1019621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-excon
Version: 0.88.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-excon with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
> RuntimeError:
> Shared Example Group: "a excon test server" called from
> ./spec/excon/test/server_spec.rb:22
> # ./lib/excon/test/plugin/server/puma.rb:12:in `start'
> #
> ./spec/support/shared_examples/shared_example_for_test_servers.rb:10:in
> `block (2 levels) in <top (required)>'
>
> Finished in 1.38 seconds (files took 0.2012 seconds to load)
> 143 examples, 1 failure
>
> Failed examples:
>
> rspec './spec/excon/test/server_spec.rb[1:3:1:2]' # Excon::Test::Server when
> the web server is puma it should behave like a excon test server starts the
> server
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec
> --pattern spec/\*\*/\*_spec.rb -c -f doc -r ./spec/spec_helper.rb failed
> ERROR: Test "ruby3.1" failed:
The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-excon/ruby-excon_0.88.0-1+rebuild1663007570_amd64-2022-09-12T18:32:50Z.build
To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you
read this, this might mean installing ruby-all-dev from experimental, or ir the
transition has alraedy started in unstable, a normal build on unstable should
do it. If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.
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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
The builds fine for me and also on repro build done on 14 Dec. Looks like a FP.
Closing.
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-excon.html
Please reopen if deemed appropriate.
On Mon, 12 Sep 2022 21:14:17 -0300 Antonio Terceiro <terce...@debian.org> wrote:
> Source: ruby-excon
> Version: 0.88.0-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: debian-r...@lists.debian.org
> Usertags: ruby3.1
>
> Hi,
>
> We are about to start the ruby3.1 transition in unstable. While trying to
> rebuild ruby-excon with ruby3.1 enabled, the build failed.
>
> Relevant part of the build log (hopefully):
> > RuntimeError:
> > Shared Example Group: "a excon test server" called from
> > ./spec/excon/test/server_spec.rb:22
> > # ./lib/excon/test/plugin/server/puma.rb:12:in `start'
> > #
> > ./spec/support/shared_examples/shared_example_for_test_servers.rb:10:in
> > `block (2 levels) in <top (required)>'
> >
> > Finished in 1.38 seconds (files took 0.2012 seconds to load)
> > 143 examples, 1 failure
> >
> > Failed examples:
> >
> > rspec './spec/excon/test/server_spec.rb[1:3:1:2]' # Excon::Test::Server
> > when the web server is puma it should behave like a excon test server
> > starts the server
> >
> > /usr/bin/ruby3.1
> > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
> > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec
> > --pattern spec/\*\*/\*_spec.rb -c -f doc -r ./spec/spec_helper.rb failed
> > ERROR: Test "ruby3.1" failed:
>
>
> The full build log is available from:
> https://people.debian.org/~terceiro/ruby3.1/17/ruby-excon/ruby-excon_0.88.0-1+rebuild1663007570_amd64-2022-09-12T18:32:50Z.build
>
> To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you
> read this, this might mean installing ruby-all-dev from experimental, or ir
> the
> transition has alraedy started in unstable, a normal build on unstable should
> do it. If you fail to reproduce, please provide a build log and diff it with
> mine so that we can identify if something relevant changed in the meantime.
>
> 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 marking it as
> 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
--
Best,
Nilesh
signature.asc
Description: PGP signature
--- End Message ---
