From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Jose Quaresma <quaresma.jose@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] sstate: show progress bar again
Date: Thu, 17 Nov 2022 12:46:51 +0100 [thread overview]
Message-ID: <lya64phkgk.fsf@ensc-pc.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <CANPvuR=SJ35jquRnLYmkBaZ=YjX-sVp9QLQGSMmU9qE996ei4g@mail.gmail.com> (Jose Quaresma's message of "Wed, 16 Nov 2022 15:36:39 +0000")
Jose Quaresma <quaresma.jose@gmail.com> writes:
>> Transition to ThreadPoolExecutor (eb6a6820928472ef194b963b606454e731f9486f)
>> broke he
>>
>> | Checking sstate mirror object availability: ...
>>
>> progress bar because the removed 'thread_worker' was still referenced
>> in an asynchronous function. As the result of the future is never
>> read, the resulting backtrace is silently discarded.
>
> I have tested the patch at the time and the progress bar works as expected,
> maybe something breaks after that.
Probably, you saw only the full 100% bar produced by
'bb.event.ProcessFinished'
But the patch does
| - def checkstatus(thread_worker, arg):
| + def checkstatus(arg):
| ...
| bb.event.fire(bb.event.ProcessProgress(msg, len(tasklist) - thread_worker.tasks.qsize()), d)
This will always raise an exception and 'bb.event.ProcessProgress' will
never be fired.
> Can the num_tasks_done be moved to there and call the first
> next(num_tasks_done) so we can remove the +1 on the ProcessProgress
I will send a v2
Enrico
next prev parent reply other threads:[~2022-11-17 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 11:24 [PATCH] sstate: show progress bar again Enrico Scholz
2022-11-16 15:36 ` [OE-core] " Jose Quaresma
2022-11-17 11:46 ` Enrico Scholz [this message]
2022-11-22 10:46 ` Jose Quaresma
2022-11-19 10:39 ` [PATCH v2] " Enrico Scholz
2022-11-22 10:51 ` Jose Quaresma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=lya64phkgk.fsf@ensc-pc.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=quaresma.jose@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.