Re: [gentoo-portage-dev] [PATCH] emerge: use asyncio interfaces for spinner during owner lookup (bug 591760)

[Zac Medico]

On Sun, Mar 26, 2017 at 7:25 PM, Zac Medico <zmedico@g.o> wrote:
> On Sun, Mar 26, 2017 at 6:58 PM, Brian Dolbec <dolsen@g.o> wrote:
>> On Sun, 26 Mar 2017 18:01:01 -0700
>> Zac Medico <zmedico@g.o> wrote:
>>
>>> X-Gentoo-bug: 591760
>>> X-Gentoo-bug-url: https://bugs.gentoo.org/show_bug.cgi?id=591760
>>> ---
>>>  pym/_emerge/depgraph.py      | 13 ++++++++-----
>>>  pym/portage/dbapi/vartree.py | 22 +++++++++-------------
>>>  2 files changed, 17 insertions(+), 18 deletions(-)
>>>
>> looks fine.
>
> Thanks, pushed:
>
> https://gitweb.gentoo.org/proj/portage.git/commit/?id=dfa317d0b8572a6c463ad5e778a8ca4633086f1b
>
>> Question, will this help make the spinner more consistent with spin?
>
> Well, that problem was already solved for the case where emerge is
> looking up owners of files, which is the case that this code affects.
>
> I'm sure there are plenty of other places where the spinner does not
> update consistently. This occurs when the main (and only) thread goes
> for a long time without calling depgraph._spinner_update(). For
> example, some of the code called via the
> depgraph._process_slot_conflicts method might we consuming a lot of
> time without calling the _spinner_update method.

When the spinner appears to be stuck, you can send a SIGUSR1 signal to
the emerge process, and then use 'bt' to get a backtrace so that we
can see what it's doing.
-- 
Thanks,
Zac