Date: Sun, 24 Apr 2022 09:57:17 +0000 From: Rene Ladan <rene@freebsd.org> To: Pau Amma <pauamma@gundo.com> Cc: freebsd-ports@freebsd.org Subject: Re: Chromium and Iridium consistently not building for 123amd64 latest Message-ID: <YmUe/ZTfEyiq3mF5@freefall.freebsd.org> In-Reply-To: <e18fee3f2d9b81f23b75fe37ca2a3f09@gundo.com> References: <171EBF3C-350D-4C4B-A589-4966F3118B28.ref@yahoo.com> <171EBF3C-350D-4C4B-A589-4966F3118B28@yahoo.com> <e18fee3f2d9b81f23b75fe37ca2a3f09@gundo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 18, 2022 at 11:38:36PM +0000, Pau Amma wrote: > On 2022-04-18 22:10, Mark Millard wrote: > > Looking at the log shows other failures during 97% : > > [massive snip] > > > I suspect that the rest of the time was its very slow scanning > > of the huge log file to report on the type of failure. This can > > take 2+ hours of itself before the actual kill happens. > > > > As I remember, something like 34 hours is about the maximum > > time before the process is started that leads to killing a > > builder. So things can be odd if it fails when it has gotten > > sufficiently near that time frame. > > That doesn't really help me figure out how to help either Iridium or > Chromium (I don't need both, and if I get to choose, I'll choose > Iridium) get a 123amd64 package. > Perhaps it are buid timeouts causing this, it builds 12.3 builds fine in poudriere on my quadcore 2015 laptop (I tested the upcoming Chromium 101 on 12.3-i386 quarterly yesterday). René
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YmUe/ZTfEyiq3mF5>