Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#1015084: ruby-rubame: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: pairs = client.recvfrom(20000)

0 views
Skip to first unread message

Lucas Nussbaum

unread,
Jul 16, 2022, 10:10:03 AM7/16/22
to
Source: ruby-rubame
Version: 0.0.3~git20131224.f3c78ba-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> Failure/Error: pairs = client.recvfrom(20000)
>
> IOError:
> recv for buffered IO
> # ./spec/rubame_spec.rb:97:in `recvfrom'
> # ./spec/rubame_spec.rb:97:in `block (3 levels) in <top (required)>'
> # ./spec/rubame_spec.rb:96:in `each'
> # ./spec/rubame_spec.rb:96:in `block (2 levels) in <top (required)>'
>
> Deprecation Warnings:
>
> Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }` instead. Called from /<<PKGBUILDDIR>>/spec/rubame_spec.rb:6:in `block (2 levels) in <top (required)>'.
>
>
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
>
> 1 deprecation warning total
>
> Finished in 0.69634 seconds (files took 0.16716 seconds to load)
> 4 examples, 1 failure
>
> Failed examples:
>
> rspec ./spec/rubame_spec.rb:62 # Rubame::Server should be able to send a message to a client
>
> /usr/bin/ruby3.0 -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 --format documentation failed
> ERROR: Test "ruby3.0" failed:


The full build log is available from:
http://qa-logs.debian.net/2022/07/16/ruby-rubame_0.0.3~git20131224.f3c78ba-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220716&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 marking 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.

Debian Bug Tracking System

unread,
Aug 17, 2022, 7:00:04 PM8/17/22
to
Your message dated Wed, 17 Aug 2022 22:53:34 +0000
with message-id <E1oORuo-...@fasolo.debian.org>
and subject line Bug#1015084: fixed in ruby-rubame 0.0.3~git20131224.f3c78ba-3
has caused the Debian Bug report #1015084,
regarding ruby-rubame: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: pairs = client.recvfrom(20000)
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.)


--
1015084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
0 new messages