Date: Mon, 18 Apr 2022 23:38:36 +0000 From: Pau Amma <pauamma@gundo.com> To: freebsd-ports@freebsd.org Subject: Re: Chromium and Iridium consistently not building for 123amd64 latest Message-ID: <e18fee3f2d9b81f23b75fe37ca2a3f09@gundo.com> In-Reply-To: <171EBF3C-350D-4C4B-A589-4966F3118B28@yahoo.com> References: <171EBF3C-350D-4C4B-A589-4966F3118B28.ref@yahoo.com> <171EBF3C-350D-4C4B-A589-4966F3118B28@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- #BlackLivesMatter #TransWomenAreWomen #AccessibilityMatters #StandWithUkrainians English: he/him/his (singular they/them/their/theirs OK) French: il/le/lui (iel/iel and ielle/ielle OK) Tagalog: siya/niya/kaniya (please avoid sila/nila/kanila)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e18fee3f2d9b81f23b75fe37ca2a3f09>