Your message dated Sat, 10 Aug 2024 14:58:27 +0000
with message-id <e1scny3-00an2t...@fasolo.debian.org>
and subject line Bug#1078431: fixed in ruby-concurrent 1.2.3-3
has caused the Debian Bug report #1078431,
regarding ruby-concurrent: flaky autopkgtest on arm64: Attempt to unlock a 
mutex which is locked by another thread/fiber
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.)


-- 
1078431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-concurrent
Version: 1.2.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package because it was blocking migration of gcc-14. I noticed that it regularly fails (I tested on arm64: 3/10).

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/r/ruby-concurrent/testing/arm64/50327775/

413s      5.2) Failure/Error: subject.put(:foo)
413s
413s           ThreadError:
413s Attempt to unlock a mutex which is locked by another thread/fiber 413s # /usr/share/rubygems-integration/all/gems/rspec-support-3.13.1/lib/rspec/support/reentrant_mutex.rb:42:in `exit' 413s # /usr/share/rubygems-integration/all/gems/rspec-support-3.13.1/lib/rspec/support/reentrant_mutex.rb:27:in `synchronize' 413s # /usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/lib/rspec/core/memoized_helpers.rb:178:in `block in fetch_or_store'
413s           # org/jruby/RubyHash.java:1441:in `fetch'
413s # /usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/lib/rspec/core/memoized_helpers.rb:177:in `fetch_or_store' 413s # /usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/lib/rspec/core/memoized_helpers.rb:343:in `block in let' 413s # ./spec/concurrent/channel/buffer/unbuffered_spec.rb:239:in `block in Buffer' 413s # ./spec/support/example_group_extensions.rb:34:in `block in in_thread'
413s
413s Finished in 4 minutes 15.7 seconds (files took 8.1 seconds to load)
413s 2941 examples, 5 failures, 11 pending
413s
413s Failed examples:
413s
413s rspec ./spec/concurrent/channel/buffer/unbuffered_spec.rb:235 # Concurrent::Channel::Buffer::Unbuffered#next returns Concurrent::NULL, false when closed and no items remain 413s rspec ./spec/concurrent/channel/buffer/unbuffered_spec.rb:186 # Concurrent::Channel::Buffer::Unbuffered#next blocks when no putting and returns <item>, true when one arrives 413s rspec ./spec/concurrent/channel/buffer/unbuffered_spec.rb:205 # Concurrent::Channel::Buffer::Unbuffered#next returns <item>, true when there are multiple putting 413s rspec ./spec/concurrent/channel/buffer/unbuffered_spec.rb:221 # Concurrent::Channel::Buffer::Unbuffered#next returns <item>, true when closed and last item 413s rspec ./spec/concurrent/channel/buffer/unbuffered_spec.rb:235 # Concurrent::Channel::Buffer::Unbuffered#next returns Concurrent::NULL, false when closed and no items remain

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: ruby-concurrent
Source-Version: 1.2.3-3
Done: Jérôme Charaoui <jer...@riseup.net>

We believe that the bug you reported is fixed in the latest version of
ruby-concurrent, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1078...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérôme Charaoui <jer...@riseup.net> (supplier of updated ruby-concurrent 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 10 Aug 2024 10:10:09 -0400
Source: ruby-concurrent
Architecture: source
Version: 1.2.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Jérôme Charaoui <jer...@riseup.net>
Closes: 1078373 1078431
Changes:
 ruby-concurrent (1.2.3-3) unstable; urgency=medium
 .
   * Team upload.
 .
   * d/rules: Use javac -source/-target values from java-common
     (Closes: #1078373)
   * d/tests: mark jruby test as flaky (Closes: #1078431)
   * d/watch: remove bad extra whitespace
Checksums-Sha1:
 a786e694975d9f856839a7e7475bde2984152b6e 1707 ruby-concurrent_1.2.3-3.dsc
 3c7c56a249d1b7c74a821b25524ce6109e636186 5828 
ruby-concurrent_1.2.3-3.debian.tar.xz
 64908b08c91858b5b6399e9da317577d98fb080c 10668 
ruby-concurrent_1.2.3-3_amd64.buildinfo
Checksums-Sha256:
 810113f798182df1a4ab2799cd249d5c082aaa9281824c6d5fe49994a9b1171c 1707 
ruby-concurrent_1.2.3-3.dsc
 f4e9a6c82371559c6798d35e1eab731a153e8aa3381afcc85661ab455492321a 5828 
ruby-concurrent_1.2.3-3.debian.tar.xz
 4118b4ada3c51b04a49df3f710320ffd48daa19378ceddf6dacc2748c2718cca 10668 
ruby-concurrent_1.2.3-3_amd64.buildinfo
Files:
 89b11fa1360f9f379692eb3f58036340 1707 ruby optional ruby-concurrent_1.2.3-3.dsc
 7b94b7228756e33d68064276b3828e5a 5828 ruby optional 
ruby-concurrent_1.2.3-3.debian.tar.xz
 0a3077be8c3ec7ad8a32b8faeced822f 10668 ruby optional 
ruby-concurrent_1.2.3-3_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQTAq04Rv2xblqv/eu5pxS9ljpiFQgUCZrd37wAKCRBpxS9ljpiF
Qmz+AQDSS/1Y1DLHmklDBO5sduKFQCfhOcFHL1yA84uBtj2VUwEA+Q3JwUjKIj6c
L3n6ZW4GSeDjWrPsI6dYTzrAozYZqAQ=
=tqIp
-----END PGP SIGNATURE-----

Attachment: pgpOP4d1QpqPR.pgp
Description: PGP signature


--- End Message ---

Reply via email to