Bug 14766 - bitbake lockfile patch incorrect when running builds in deep paths
Summary: bitbake lockfile patch incorrect when running builds in deep paths
Status: VERIFIED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 4.0 M4
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2022-03-23 14:22 UTC by Mark Hatle
Modified: 2022-04-14 14:15 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Hatle 2022-03-23 14:22:46 UTC
When the path to the build directory appears to be in a deep path the system is unable to connect to the bitbake socket.

To reproduce this:

mkdir -p \
/home/fray/testsuite/project/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb/ccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

cd <same long path>

git clone https://git.yoctoproject.org/poky

. ./poky/oe-init-build-env build
bitbake-layers add-layer <long_path>/poky/meta-skeleton

Result
NOTE: Starting bitbake server...
NOTE: No reply from server in 30s
NOTE: No reply from server in 30s
Timeout while waiting for a reply from the bitbake server (60s)


Change to a shorter path (repeat this while in the 'cccccc...ccccc' path) and it works.

It appears that this may be related to connecting to the socket.
Comment 1 Mark Hatle 2022-03-23 14:25:54 UTC
This works properly in gatesgarth.


This does NOT work in honister.
Comment 2 Randy MacLeod 2022-03-24 14:33:26 UTC
In autobuilder.
Comment 4 Mark Hatle 2022-04-14 14:14:41 UTC
Verified this does fix the original reported problem.
Comment 5 Mark Hatle 2022-04-14 14:15:31 UTC
Verified this fixes the original issue.