Bug 728698 – dev-ruby/childprocess-3.0.0 fails test "ChildProcess kills the full process tree"

• Status: UNCONFIRMED
• Product: Gentoo Linux

[Description Jonathan Lovelace 2020-06-18 23:05:54 UTC]

Created attachment 645190 [details]
dev-ruby:childprocess-3.0.0:20200618-211521.log

On rebuilding due to RUBY_TARGETS changes, =dev-ruby/childprocess-3.0.0 fails its test phase because one test fails:

-----

Failures:

  1) ChildProcess kills the full process tree
     Failure/Error: raise msg

     RuntimeError:
       timed out after 30 seconds
     # ./spec/spec_helper.rb:195:in `wait_until'
     # ./spec/childprocess_spec.rb:286:in `block (3 levels) in <top (required)>'
     # ./spec/childprocess_spec.rb:281:in `block (2 levels) in <top (required)>'

Finished in 34.01 seconds (files took 0.16372 seconds to load)
68 examples, 1 failure

Failed examples:

rspec ./spec/childprocess_spec.rb:280 # ChildProcess kills the full process tree

------

I tried changing the number of seconds it waits from 30 seconds to as many as 180 seconds using sed in a pre_src_prepare() function in /etc/portage/env, but the only difference that made was to change the time the test took to time out.

[Comment 1 Jonathan Lovelace 2020-06-18 23:06:19 UTC]

Created attachment 645192 [details]
emerge-info.txt

[Comment 2 Hans de Graaff 2020-06-26 08:17:37 UTC]

I can't reproduce this. Does this also happen with 4.0.0 ?

This test appears to call "ruby". That might cause issues if that does not match the ruby being used for the tests, although in this case this doesn't look like an issue. That might also be a thing to check.

[Comment 3 Hans de Graaff 2020-06-26 08:35:20 UTC]

(In reply to Hans de Graaff from comment #2)

> This test appears to call "ruby". That might cause issues if that does not
> match the ruby being used for the tests, although in this case this doesn't
> look like an issue. That might also be a thing to check.

This has now been fixed in childprocess 4.0.0.