summaryrefslogtreecommitdiffstats
path: root/meta/lib/oeqa/core/utils/concurrencytest.py
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2019-12-03 22:01:25 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-12-06 14:39:29 +0000
commitccd7f12b1c95b546ef79204ad0832b88a595d0ea (patch)
tree04cd240e7ca62459392b8483ba3f631574524fc2 /meta/lib/oeqa/core/utils/concurrencytest.py
parent109ef2e5c4161a2c0ac58bede3daa48c7b4881ec (diff)
downloadpoky-ccd7f12b1c95b546ef79204ad0832b88a595d0ea.tar.gz
bitbake: knotty/uihelper: Switch from pids to tids for Task event management
We've seen cases where a task can execute with a given pid, complete and a new task can start using the same pid before the UI handler has had time to adapt. Traceback (most recent call last): File "/home/pokybuild/yocto-worker/qemux86-alt/build/bitbake/lib/bb/ui/knotty.py", line 484, in main helper.eventHandler(event) File "/home/pokybuild/yocto-worker/qemux86-alt/build/bitbake/lib/bb/ui/uihelper.py", line 30, in eventHandler del self.running_tasks[event.pid] KeyError: 13490 This means using pids to match up events on the UI side is a bad idea. Change the code to use task ids instead. There is a small amount of fuzzy matching for the progress information since there is no task information there and we don't want the overhead of a task ID in every event, however since pid reuse is unlikely, we can live with a progress bar not quite working properly in a corner case like this. [YOCTO #13667] (Bitbake rev: e427eafa1bb04008d12100ccc5c862122bba53e0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/lib/oeqa/core/utils/concurrencytest.py')
0 files changed, 0 insertions, 0 deletions