From nobody Wed Aug 5 13:08:51 2026 X-Original-To: questions@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 4hFW2H0vQZz6nFNF for ; Wed, 05 Aug 2026 13:08:55 +0000 (UTC) (envelope-from fbsd.questions@palaceofretention.ca) Received: from mail.vinnythegeek.ca (mail.vinnythegeek.ca [66.183.142.13]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4hFW2G2gKXz3ZG5 for ; Wed, 05 Aug 2026 13:08:54 +0000 (UTC) (envelope-from fbsd.questions@palaceofretention.ca) Authentication-Results: mx1.freebsd.org; none Received: from [192.168.60.59] (unknown [192.168.60.59]) by mail.vinnythegeek.ca (Postfix) with ESMTPSA id 7D74069E; Wed, 05 Aug 2026 06:08:51 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.vinnythegeek.ca 7D74069E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=palaceofretention.ca; s=all-mail; t=1785935331; bh=Wjra5C/oDxSUI8xN+cz/hX7vvrCDw+rrQ0HdoR/wHV0=; h=Date:Subject:To:References:From:In-Reply-To; b=QYFj70Sy/OHtHhIfy2vy/sNUr7alJMonV+NcpsyG8PqTS5WuwKD9zmcrqyKVqlVgM pLuN5MVMBjUwwpmJ+LtURnna1oWlLZ18s4WaiQ4fL9zGaupPr9B0ZB7f5hmRLPV8NQ fFokQdkYxa/b4IFDx/mRQW92oQMcrCZT2qA/fKTk= Message-ID: <564e15e8-cca9-4c4b-818b-e19319fcedf0@palaceofretention.ca> Date: Wed, 5 Aug 2026 06:08:51 -0700 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Chromium availability. To: Johannes-Maria Kaltenbach , questions@freebsd.org References: <4cc52e97-de21-47e2-baac-275d12aed1b5@palaceofretention.ca> <418ae9091e90abaf0f9ea6dbf70b72f45068000f.camel@telaman.net.au> <20260805092829.GA3425@jmk1.org> Content-Language: en-US, en-CA From: "Mark G." In-Reply-To: <20260805092829.GA3425@jmk1.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4hFW2G2gKXz3ZG5 X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:852, ipnet:66.183.0.0/16, country:CA] X-Spamd-Bar: ---- On 8/5/26 02:28, Johannes-Maria Kaltenbach wrote: > Hello, > > just for your information: > > On Tue, Aug 04, 2026 at 07:59:17PM -0700, Mark G. wrote: >> On 8/4/26 19:35, David wrote: >>> On Tue, 2026-08-04 at 19:31 -0700, Mark G. wrote: >>>> On 8/4/26 19:26, David wrote: >>>>> On Tue, 2026-08-04 at 18:56 -0700, Mark G. wrote: >>>>>> On 8/4/26 18:51, David wrote: > ... >> I am running 14.4-RELEASE-p8, on another system and see >> that chromium is missing from "latest" and "quarterly" >> (I am just showing quarterly below, switching to latest >> gives the same results): > > same version here. > On 14 I was never able to install chromium; it always ended > in a timeout (after 24 hours). > Perhaps that's why it isn't in the repository? > > from the poudriere log: > > [00:01:08] [01] [00:00:00] Building www/chromium | chromium-148.0.7778.96 > [00:01:08] [01] [00:00:00] Status www/chromium | chromium-148.0.7778.96: check-sanity > [00:01:18] [01] [00:00:10] Status www/chromium | chromium-148.0.7778.96: pkg-depends > [00:01:19] [01] [00:00:11] Status www/chromium | chromium-148.0.7778.96: fetch-depends > [00:01:19] [01] [00:00:11] Status www/chromium | chromium-148.0.7778.96: fetch > [00:01:55] [01] [00:00:47] Status www/chromium | chromium-148.0.7778.96: checksum > [00:02:00] [01] [00:00:52] Status www/chromium | chromium-148.0.7778.96: extract-depends > [00:02:00] [01] [00:00:52] Status www/chromium | chromium-148.0.7778.96: extract > [00:03:00] [01] [00:01:52] Status www/chromium | chromium-148.0.7778.96: patch-depends > [00:03:01] [01] [00:01:53] Status www/chromium | chromium-148.0.7778.96: patch > [00:03:03] [01] [00:01:55] Status www/chromium | chromium-148.0.7778.96: build-depends > [00:06:12] [01] [00:05:04] Status www/chromium | chromium-148.0.7778.96: lib-depends > [00:06:53] [01] [00:05:45] Status www/chromium | chromium-148.0.7778.96: configure > [00:07:27] [01] [00:06:19] Status www/chromium | chromium-148.0.7778.96: build > [1D:00:07:42] [01] [1D:00:06:34] Status www/chromium | chromium-148.0.7778.96: timeout > [1D:00:44:46] [01] [1D:00:43:38] Finished www/chromium | chromium-148.0.7778.96: Failed: build/timeout > > > I don't depend on chromium, so I ignored it. > Is there a built-in timeout in poudriere? > There are indeed a couple of knobs that need setting in: /usr/local/etc/poudriere.conf In no particular order (I had some file limit fails, so bumped this up): # How many file descriptors to limit each jail process to (default: 1024) # This can also be set per PKGBASE, such as MAX_FILES_RStudio=2048. # Package names with hyphens (-) should be replaced with underscores (_). MAX_FILES=4096 The one you're looking for (I set to 10 days, and chromium finishes): # This defines the max time (in seconds) that a command may run for a build # before it is killed for taking too long. Default: 86400 MAX_EXECUTION_TIME=864000 I also lowered PARALLEL_JOBS from the max (32 in my case) to less, so I would have CPUs available for other things than the builder. # parallel build support. # # By default poudriere uses hw.ncpu to determine the number of builders. # You can override this default by changing PARALLEL_JOBS here, or # by specifying the -J flag to bulk/testport. # # Example to define PARALLEL_JOBS to one single job PARALLEL_JOBS=28 I also disabled the use of TMPFS (and some failures stopped): # Use tmpfs(5) # This can be a space-separated list of options: # wrkdir - Use tmpfs(5) for port building WRKDIRPREFIX # data - Use tmpfs(5) for poudriere cache/temp build data # localbase - Use tmpfs(5) for LOCALBASE (installing ports for packaging/testing) # all - Run the entire build in memory, including builder jails. # yes - Enables tmpfs(5) for wrkdir and data # no - Disable use of tmpfs(5) # EXAMPLE: USE_TMPFS="wrkdir data" # Disable 20240916 see if build problems go away USE_TMPFS=no