Packages buildbot is erratic, both master and 23.05 packages fail often
Petr Štetiar
ynezz at true.cz
Sat Jun 3 23:46:02 PDT 2023
Hannu Nyman <hannu.nyman at iki.fi> [2023-06-03 11:27:03]:
> Petr Štetiar kirjoitti 2.6.2023 klo 22.07:
> > So having following in buildbot log:
> >
> > 2023-06-01 23:53:12+0000 [-] command timed out: 3600 seconds without output running [b'make', b'-j7', b'IGNORE_ERRORS=n m y', b'BUILD_LOG=1', b'CONFIG_AUTOREMOVE=y', b'CONFIG_SIGNED_PACKAGES='], attempting to kill
> > 2023-06-01 23:53:12+0000 [-] trying to kill process group 1528179
> >
> > I've looked at the system logs around that time and found following:
> >
> > Jun 01 22:23:19 audit[3844576]: AVC apparmor="DENIED" operation="mkdir" info="Failed name lookup - name too long"
> > error=-36 profile="docker-default"
> > name="/shared-workdir/build/sdk/build_dir/hostpkg/gettext-0.21.1/gettext-tools/confdir3/confdir3/confdir3/confdir3...[snip very long repeating pattern]...
> > confdir3/confdir3/confdir3/confdir3/confdir3" pid=3844576 comm="conftest" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
> > Jun 01 22:23:45 kernel: conftest[3855174]: segfault at 0 ip 00007fe9581067e7 sp 00007ffd94ca2118 error 4 in libc-2.31.so[7fe958085000+159000]
> > ...
> >
> > Since the host is shared with other 3 build workers I can't be sure, that it
> > originated from that timeouted build.
> >
>
> Looking at that observation about gettext and recursive "confdir3/", it is
> plausible that gettext has problem that manifests in some builds, or trouble
> with parallelism on some occasions.
I looked into this further and its probably harmless (?) error caused by the
Docker default Apparmor profile in configure checks around max path:
tar-1.34/m4/getcwd-path-max.m4:#define DIR_NAME "confdir3"
tar-1.34/configure:#define DIR_NAME "confdir3"
I think it's harmless as its present on all other build workers as well.
Cheers,
Petr
More information about the openwrt-devel
mailing list