From nobody Sun Apr 24 09:57:17 2022 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id B733B199596F for ; Sun, 24 Apr 2022 09:57:17 +0000 (UTC) (envelope-from rene@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KmNq14qz2z3tMl; Sun, 24 Apr 2022 09:57:17 +0000 (UTC) (envelope-from rene@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1650794237; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=oRjjtahSZJHTtc1W6Os+5VpRf05CVi/kXuZx8vdxVn8=; b=A9gARmwRT6DxjlNI7peccSuLkAmwFNIKW4luJCxQoKhhjvjnyrWq/l8yD/X/UNIlN8u7bq OH2cfjDO4hedpSAwrHVecNd5HnadIndBh8Rsuqey6A+BPlZnbFuK/Dav55TGPqGuLORsAF p/I1yPgxbxKD5pKcVUYa6ORDsxVbvIYv/QEPLSv4FOKNE0CtD08Fo9CLXqAWc1SX1B5QRc I59jd7S+INxUk/0iQSPuciP4KuTBYNRq4raVj9sTueiWmI+5hfA29XHB8nliKuhIBLizmq kvWeV3B7dKX9WHrjrIZmX0bODuT9j75mjL9H3N3QheGEl7mMQAETraNaqM2grQ== Received: by freefall.freebsd.org (Postfix, from userid 1185) id 8C4B019950; Sun, 24 Apr 2022 09:57:17 +0000 (UTC) Date: Sun, 24 Apr 2022 09:57:17 +0000 From: Rene Ladan To: Pau Amma Cc: freebsd-ports@freebsd.org Subject: Re: Chromium and Iridium consistently not building for 123amd64 latest Message-ID: References: <171EBF3C-350D-4C4B-A589-4966F3118B28.ref@yahoo.com> <171EBF3C-350D-4C4B-A589-4966F3118B28@yahoo.com> List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1650794237; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=oRjjtahSZJHTtc1W6Os+5VpRf05CVi/kXuZx8vdxVn8=; b=p7/io+aUV9vWlqeE7JI2FuGnQEWYfcGii/C59SvC6dk2hj50KeuHtALgHR5ZBObu/0gnab DyaqLjJ4JNXcDtHwk5fR6H+G1z42A19IpPf1ULXyTTCGHS0qJVGuSDfx3vXSVS3d0KOfqX 5L2SJ+1aDnX9N6DXpFsxeNE3deDN5NE/xM+DlGxz0T7HznpY6GldyDUnQQnLv+NzzREPRL Gw/GjKFHMTk+15js3p8CEX7GbyghYX9d4OHhp35q7/kCrRG+MkMn32UES0VRVDtxg/e2uk lgrmZfVu3O+VNqCuX2BMnpEnQAgw+csSoddY+NwOlYPq9ohj+Qdqyv7Tk1gOog== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1650794237; a=rsa-sha256; cv=none; b=Hj7j/cwirCTWqWN4oNNo2DcDnCJ2ZCNEbE3y3XYDniFletoNCjagqdTf0I745dY1LC3TfK qSYVWS8eGl8vKoaHTmamgwgeC3TMgA28MPM+tVMe+7F9Pz3080Do3+5cUuGXyq2s+5Vzwk su1DcpuEAKAYRy2jDTkK8VFD9EjI7XHDP0SwrX2SOZyabn+P7QZmvXX0NiWn0P7xrZDpaZ +eHJJJIM+g0fpjVtAUOETj4f7HyyojYbeEj88cJ3unrKEydgpjRxzscT/QVKM1h+ryIWRK 6RXsxm/kLxWZ9NY9nEAOXG+Z14l39c0LtNV9vjpWGpdK0RoQ3WdbOUFxD0NFaA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N 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é