But why should this be set in core for everyone, and to ten minutes? Your
farm is misconfigured if 40 seconds is not enough got ‘git status’.
Alex
On Tue 18. Feb 2025 at 0.39, hongxu via lists.openembedded.org wrote:
> It happens occasionally, in our build farm, similar Yocto Autobuilder, the
>
It happens occasionally, in our build farm, similar Yocto Autobuilder, the
build test controller starts up multiple containers for the build on the host,
and each container is allocated for the world build.
It should be some kind of limit testing or stress testing for yocto build
-=-=-=-=-=-=-=
On 17 Feb 2025, at 07:46, hongxu via lists.openembedded.org
wrote:
>
> The environment variable SETUPTOOLS_SCM_SUBPROCESS_TIMEOUT allows to override
> the subprocess timeout. The default is 40 seconds and should work for most
> needs.[1] However, it was not enough while using git shallow tarball
The environment variable SETUPTOOLS_SCM_SUBPROCESS_TIMEOUT allows to override
the subprocess timeout. The default is 40 seconds and should work for most
needs.[1] However, it was not enough while using git shallow tarball and
starting
multiple Yocto world builds in one host.
| File "tmp/work/x8
