BuildStream attempts to create very long filenames after finisihing a build
Summary
When building specific projects, apparently only on debian, BuildStream fails consistently with "File name too long" when attempting to recursively symlink debug files.
The symlink will point to a file in /lib/debug/tools/, but the debug base path is repeated (i.e. /lib/debug/tools/lib/debug/tools/lib/debug/tools/.../libcc1.so.0.0.0.
Steps to reproduce
No steps yet, but has been reproduced by two users. Notable similarities were the use of debian (switching to ubuntu apparently solved the issue), building a stage1 gnu toolchain and the fact that both failed to create a symlink to the same debug files.
What is the current bug behavior?
BuildStream fails to build because it seems to create a recursive file path.
What is the expected correct behavior?
BuildStream should not create a recursive file path, and pass the build.
Relevant logs and/or screenshots
- Reproduced in GitLab CI: https://gitlab.com/trustable/distros/minimal-distro/-/jobs/93411861
- A paste of a similar error: https://paste.gnome.org/pqfh04sb2#line-2
- BuildStream version affected: /milestone %BuildStream_v1.2
Edited by Tristan Maat