On Mon, Mar 31, 2014 at 3:57 PM, Dominique Dumont
<dominique.dum...@hp.com> wrote:
>
> Hello
>
> Package build of ruby-pygments.rb version
> 91f0ef32d7accf4de83e099d164781c48d523a8f
> works, well sort of works.
>
>
> The package build and test do not return errors. But 2 pythons processes go
> on running 100% CPU for tens of seconds after the package build is finished.
>
> The running processes are:
> python2
> [...]/pkg-ruby-extras/build-area/ruby-pygments.rb-0.5.0~git.20130605.84c69a1/lib/pygments/mentos.py
> python2
> [...]/pkg-ruby-extras/build-area/ruby-pygments.rb-0.5.0~git.20130605.84c69a1/lib/pygments/mentos.py
>
> So something is seriously wrong in the way ruby-pygments is controlling
> the python-pygments processes.
>
> I don't think reasonable to send this package to Debian build system until
> this problem is fixed.
I found out what causes this problem: for some reason popen4 dose not
report the correct pid (or some such) and it is not killed correctly. The cpu
pegging can be reproduced by running the test case
test_returns_nil_on_timeout.
I have created a fix and forwarded it for upstream inclusion
https://github.com/tmm1/pygments.rb/pull/119
When this is accepted upstream I intend to go forth with repackaging
the upstream tarball and removing the vendor directory entirely.
--
Per
--
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/cabyrxss6wtkbu+6tasa6cpty-axjrx84palqc6bj-rzgmlg...@mail.gmail.com
