Date: Mon, 20 Jan 2025 16:17:18 -0800 From: Mark Millard <marklmi@yahoo.com> To: Mark Linimon <linimon@portsmon.org>, Ronald Klop <ronald-lists@klop.ws> Cc: freebsd-arm@freebsd.org, "freebsd-pkg@freebsd.org" <freebsd-pkg@FreeBSD.org>, FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: trimming_ignore poudriere failure [134releng-armv7-quarterly also failed, still no armv7 2025Q1 build in process] Message-ID: <61EBD844-922A-411B-93DF-8AD6EECCD4EB@yahoo.com> In-Reply-To: <6EA6FE58-BB10-418C-86C3-9A8F6BAE80FF@yahoo.com> References: <4226686C-BADB-4D9D-9CF9-54C3AF1692EB.ref@yahoo.com> <4226686C-BADB-4D9D-9CF9-54C3AF1692EB@yahoo.com> <1710947431.3032.1737106880170@localhost> <893896323.1642003.1737126216196@privateemail.com> <D4550DBA-3824-40D5-9DF0-1561821895EA@yahoo.com> <6EA6FE58-BB10-418C-86C3-9A8F6BAE80FF@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 17, 2025, at 21:00, Mark Millard <marklmi@yahoo.com> wrote: > On Jan 17, 2025, at 10:19, Mark Millard <marklmi@yahoo.com> wrote: >=20 >> On Jan 17, 2025, at 07:03, Mark Linimon <linimon@portsmon.org> wrote: >>=20 >>> On 01/17/2025 3:41 AM CST Ronald Klop <ronald-lists@klop.ws> wrote: >>> See latest 141releng-armv7-quarterly = (https://pkg-status.freebsd.org/ampere1/jail.html?mastername=3D141releng-a= rmv7-quarterly) failure: https://pkg-status.freebsd.org/ampere1/. >>>=20 >>> The part of the logs about this error are not public (AFAIK) >>=20 >> The machine is only accessible by IPv6. I have a 6 to 4 bridge = running and >> I was able to access them. >>=20 >> I have access to any bulk build logs and I expect Ronald does too. >> that includes to: >>=20 >> = https://pkg-status.freebsd.org/ampere1/data/141releng-armv7-quarterly/93a8= 6df99a36/logs/ >>=20 >> and to the the (here) empty: >>=20 >> = https://pkg-status.freebsd.org/ampere1/data/141releng-armv7-quarterly/93a8= 6df99a36/logs/errors/ >>=20 >> The type of log showing any error information would not seem to be >> port/package specific but more like what what should show the >> poudriere commands themselves: logs from outside the builder process >> instead of/from inside a builder process. >>=20 >> As for what can be seen from odd/incomplete content for logs for = inside builder process . . . >>=20 >> There are several logs that are incomplete (all stop with >> "---Begin Environment---") but that do not report any errors. > . . . >=20 > An interesting point for almost all of the too-small log files > (not for the one later example of a zero-size log) . . . >=20 > = https://github.com/freebsd/poudriere/blob/3.4.2/src/share/poudriere/common= .sh >=20 > has: >=20 > echo "---Begin Environment---" > injail /usr/bin/env > echo "---End Environment---" >=20 > which only has "injail /usr/bin/env" before the next echo > and the /usr/bin/env output also did not show up either. >=20 > Some sort of racy "injail" failure specific to armv7, > given the usual lack of failure? >=20 > Some sort of racy "/usr/bin/env" failure specific to armv7, > given the usual lack of failure? (Possibly only for jail > contexts?) FYI: 134releng-armv7-quarterly for 93a86df99a36 also got a failure that leads to "trimming_ignore:" being as far as the status goes: default quarterly 134releng-armv7 93a86df99a36 0 0 0 700 1291 -1991 = trimming_ignore: Mon, 20 Jan 2025 21:39:37 GMT 00:04:14 ampere1 There are, again, a bunch of short logs that end just after: "---Begin Environment---". So, again it is going to be a notable time before armv7 gets a 2025Q1 build, even if the eventual next *releng-armv7 build attempt works. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?61EBD844-922A-411B-93DF-8AD6EECCD4EB>