On Thu, 2011-06-23 at 07:04 -0400, Josef Skladanka wrote:
> Hello,
>
> yesterday, Kamil spotted some depcheck run, which took quite a lot
> of
> time.
> It was caused by the depcheck_pretty() routines, which took some
> time
> to parse those 70k lines of text. Sadly, this is not-a-bug, but a
> feature. The positive thing is, that logs this long are not common
> and
> mostly sign a error in dependencies.
Thanks for the heads up Josef. What sort of delays are you seeing? Is
this minutes or hours?
Yesterday I ran depcheck and it checked lots of perl packages (hundreds of dependencies).
Depcheck/yum spit out thousands of lines (the whole log was about 6 MB IIRC).
Depcheck_pretty found 70 000 lines related to depsolving problems. All lines are checked
with regular expressions. Several thousand of lines were highlighted, causing pretty_log
also to take some time to process. Overall it added around 5 minutes to the test length.
It's not convenient, but I don't consider it a problem at the moment. Usually the
logs are much shorter and there is no noticeable delay.