summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/taskdata.py
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2022-12-13 23:16:02 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-12-13 23:26:28 +0000
commit77a9c9b66b26563729d35f8f7ee957d623659fe8 (patch)
treefe873b3000747f0980c918df888b192a9bab49cc /bitbake/lib/bb/taskdata.py
parent9c36aef6102a691b8cc5fdc43f7f24bb7fe665db (diff)
downloadpoky-77a9c9b66b26563729d35f8f7ee957d623659fe8.tar.gz
bitbake: main/process: Add extra sockname debugging
We're struggling to understand how bitbake.sock can sometimes disappear in live builds when we can't see where it could have been deleted. This causes connection failures to the server and failed builds. Add some extra debugging around the server log and client retry log messages to give more information for the next time this issue occurs. (Bitbake rev: 376a516dc8c96727fd042ada65f803013601ee2d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/taskdata.py')
0 files changed, 0 insertions, 0 deletions