Date: Sat, 25 Jan 2025 19:57:27 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: David Wolfskill <david@catwhisker.org> Cc: freebsd-ports@freebsd.org, chromium@freebsd.org Subject: Re: Packaging poudriere-built www/chromium fails...? Message-ID: <Z5UmB1QszhgRNLB7@kib.kiev.ua> In-Reply-To: <Z5UZ72Uea3NeNdrz@albert.catwhisker.org> References: <Z5UZ72Uea3NeNdrz@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 25, 2025 at 09:05:51AM -0800, David Wolfskill wrote: > TL;DR: poudriere build log for www/chromium ends with: > ... > =========================================================================== > =======================<phase: package >============================ > ===== env: 'PKG_NOTES=build_timestamp built_by' 'PKG_NOTE_build_timestamp=2025-01-25T15:03:22+00:00' 'PKG_NOTE_built_by=poudriere-git-3.4.99.20250115' NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 > ===> Building packages for chromium-132.0.6834.110 > ===> Building chromium-132.0.6834.110 > pkg-static: Unable to access file /wrkdirs/usr/ports/www/chromium/work/stage/usr/local/share/chromium/headless_lib_data.pak:No such file or directory > pkg-static: Unable to access file /wrkdirs/usr/ports/www/chromium/work/stage/usr/local/share/chromium/headless_lib_strings.pak:No such file or directory > *** Error code 1 > > Stop. > make: stopped in /usr/ports/www/chromium > =>> Cleaning up wrkdir > ===> Cleaning for chromium-132.0.6834.110 > build of www/chromium | chromium-132.0.6834.110 ended at 2025-01-25T16:39:43+00:00 > build time: 01:36:21 > !!! build failure encountered !!! > > -----------%<------------------------------------------------------- > > Some relevant details: > The build host is running: > freebeast(14.2-S)[11] uname -aUK > FreeBSD freebeast.catwhisker.org 14.2-STABLE FreeBSD 14.2-STABLE #91 stable/14-n270226-6a0afbcbf6a0: Sat Jan 25 12:05:37 UTC 2025 root@freebeast.catwhisker.org:/common/S1/obj/usr/src/amd64.amd64/sys/GENERIC amd64 1402501 1402501 > > The ports tree is at main-n693103-115d03a10d18 > > The builder is building packages under stable/14 (amd64) for use > by systems running stable/14 (amd64). (It's intended to be simple.) > > This was from a regular (twice-weekly) "poudriere bulk" run; none > of the other ports/packages had an issue (except editors/abiword, > but that's been an issue for several weeks, and thus does not seem > to be relevant to the current issue). > > chromium-131.0.6778.204_2 had built just fine on 20 January. > > I tried the failing build a couple of times. the first time, > poudriere's summary was: > > [01:59:14] Failed ports: editors/abiword:build www/chromium:package > [01:59:14] [14amd64-ports-home] [2025-01-25_12h55m35s] [committing] Time: 01:59:12 > Queued: 119 Inspected: 0 Ignored: 0 Built: 117 Failed: 2 Skipped: 0 Fetched: 0 Remaining: 0 > [01:59:14] Logs: /tank/poudriere/poudriere/data/logs/bulk/14amd64-ports-home/2025-01-25_12h55m35s > [01:59:14] Cleaning up > > I then modified some local patches I have (for games/xjig) & re-ran > the "poudriere bulk"; the summary this time was: > > [01:37:06] Removing old packages > [01:37:06] Built ports: games/xjig > [01:37:06] Failed ports: editors/abiword:build www/chromium:package > [01:37:06] [14amd64-ports-home] [2025-01-25_15h02m47s] [committing] Time: 01:37:04 > Queued: 3 Inspected: 0 Ignored: 0 Built: 1 Failed: 2 Skipped: 0 Fetched: 0 Remaining: 0 > [01:37:06] Logs: /tank/poudriere/poudriere/data/logs/bulk/14amd64-ports-home/2025-01-25_15h02m47s > [01:37:06] Cleaning up Me too. Added chromium@ to Cc. > > (I note that the previous package for chromium-131.0.6778.204_2 was > apparently removed, with nothing to replace it. Not really a huge > issue, but a bit inconvenient.) I use ATOMIC_PACKAGE_REPOSITORY=yes COMMIT_PACKAGES_ON_FAILURE=yes KEEP_OLD_PACKAGES=yes KEEP_OLD_PACKAGES_COUNT=15 to rebuild pkg repo on failure, and to keep previous 15 builds, exactly for such cases. > > I would file a bug report, but at this point, I don't know if one > should be filed against poudriere, chromium, both, or something > else entirely. > > So if anyone has a clue to share, I would welcome that.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Z5UmB1QszhgRNLB7>