Hi ruby-msgpack maintainers,

On 01-12-2024 12:13, Paul Gevers wrote:
I'll probably NMU once I confirm it builds on debomatic.

I just tested this on our porterbox and my patch isn't enough. With the patch, the test seems to hang. I had to disable the following tests to finish the tests. It *seems* that either the test runs quickly, within seconds, or gets a process at 100% cpu for at least several minutes. Killing the build doesn't kill the job that takes 100% cpu by the way, it remains running in the background. Killing it with sigterm didn't work, I used sigkill.

spec/cases_spec.rb
spec/cruby/buffer_io_spec.rb
spec/cruby/buffer_packer.rb
spec/cruby/buffer_spec.rb
spec/ext_value_spec.rb
spec/factory_spec.rb
spec/format_spec.rb
spec/msgpack_spec.rb

Weirdly enough, when I started disabling tests in a different order, I also got a passing set with only disabling these:

spec/msgpack_spec.rb
spec/packer_spec.rb
spec/unpacker_spec.rb

So the different tests also influence each other and the order matters. Even more weirdness, when I run each test stand alone, or only these latest three, they pass.

ruby-msgpack is in the key package set. Can somebody with ruby expertise please have a look.

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to