Date: Sun, 24 Apr 2022 22:12:29 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: Rene Ladan <rene@freebsd.org> Cc: Pau Amma <pauamma@gundo.com>, freebsd-ports@freebsd.org Subject: Re: Chromium and Iridium consistently not building for 123amd64 latest Message-ID: <tkrat.7dfbcdc4f0106d92@FreeBSD.org> References: <171EBF3C-350D-4C4B-A589-4966F3118B28.ref@yahoo.com> <171EBF3C-350D-4C4B-A589-4966F3118B28@yahoo.com> <e18fee3f2d9b81f23b75fe37ca2a3f09@gundo.com> <YmUe/ZTfEyiq3mF5@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24 Apr, Rene Ladan wrote: > 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. I ran into this issue recently with a non-standard build of openoffice that produced multi-GB log files. The scan was taking > 24 hours. It might be more efficient to use a sed script that quits on first match instead of all of those greps. Something using hyperscan would probably be even better.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?tkrat.7dfbcdc4f0106d92>