Package: ruby-childprocess Version: 2.0.7-1 Usertags: goto-cc Despite package build seemingly completing with success, the following processes continue to live, which causes builds in a chroot to fail as the build place cannot be unmounted:
1001 23103 0.0 0.0 35880 6656 ? Sl May10 0:00
/usr/bin/ruby2.0 -e sleep
1001 23113 0.0 0.0 35876 6648 ? Sl May10 0:00
/usr/bin/ruby2.0 -e sleep
1001 30751 0.0 0.0 39204 7316 ? Sl May10 0:00
/usr/bin/ruby2.1 -e sleep
1001 30766 0.0 0.0 39120 7320 ? Sl May10 0:00
/usr/bin/ruby2.1 -e sleep
Indeed the build process appears to be aware of this, but ignores the problem:
[...]
Running tests for ruby2.0 with test file list from debian/ruby-test-files.yaml
...
[...]
...............*.....................
Pending:
ChildProcess lets a detached child live on
# how do we spec this?
# ./spec/childprocess_spec.rb:139
Finished in 4.12 seconds
37 examples, 0 failures, 1 pending
Running tests for ruby2.1 with test file list from debian/ruby-test-files.yaml
...
[...]
...............*.....................
Pending:
ChildProcess lets a detached child live on
# how do we spec this?
# ./spec/childprocess_spec.rb:139
Finished in 4.24 seconds
37 examples, 0 failures, 1 pending
Best,
Michael
pgpCXsX00ZqXT.pgp
Description: PGP signature
