Date: Tue, 11 Feb 2025 14:15:38 -0800 From: Mark Millard <marklmi@yahoo.com> To: Robert Clausecker <fuz@fuz.su> Cc: freebsd-arm <freebsd-arm@freebsd.org>, FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: 141releng-armv7-quarterly stuck in run-depends status for octave-forge-20241116: 34:28:33 for package build so far Message-ID: <7E7100A8-FDC1-4636-8F06-3C7DC8A9AF50@yahoo.com> In-Reply-To: <Z6u9hchxHVE4GwGu@fuz.su> References: <0601C3C9-FABC-482C-A42B-0C707769D065.ref@yahoo.com> <0601C3C9-FABC-482C-A42B-0C707769D065@yahoo.com> <Z6syiwixIGol_8I9@fuz.su> <0792121A-3B7D-465F-A2BB-D2A095DF5A7A@yahoo.com> <Z6u9hchxHVE4GwGu@fuz.su>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Robert, On Feb 11, 2025, at 13:13, Robert Clausecker <fuz@fuz.su> wrote: > Am Tue, Feb 11, 2025 at 12:01:10PM -0800 schrieb Mark Millard: >> It did finish --after 39:49:02 . >>=20 >> As long as the O(n=C2=B2) build-time problem exists: Is the >> package's build worth the delays to most other package >> builds that are done on on any specific builder machine? >>=20 >> ampere1 cycles through building and distributing: >> 141arm64-quarterly >> 141releng-armv7-quarterly >> 1341arm64-quarterly >> 134releng-armv7-quarterly >>=20 >> ampere3 is similar (default here is a.k.a. latest): >> 141arm64-default >> 141releng-armv7-default >> 1341arm64-default >> 134releng-armv7-default >>=20 >> If the armv7's all have that time problem, the >> problem looks to adds days to the time to complete >> a cycle of 4 types of builds. >>=20 >>> The reason why you see this only now is that I have recently pushed = a patch >>> to fix math/octave on armv7; previously it didn't build.=3D >>=20 >> Should the package be considered broken for armv7 until >> it is fixed to build in a normal time frame instead of >> an O(n=C2=B2) tiem frame, just because it takes too long as >> stands? >=20 > Yes, please mark it as broken. It's only a metaport, so no > functionality is lost by not providing it. > The underlying problem should be fixed. I'm not a committer --or even a maintainer of anything. So I can not be the one to make the actual "mark it as broken" commit. Are you looking for a bugzilla submittal with a patch to add something like: BROKEN_armv7=3D armv7 builds are spending, e.g., 39:49:02 in an = N-squared-process. before the USES=3D line in the Makefile? =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?7E7100A8-FDC1-4636-8F06-3C7DC8A9AF50>