While building ports on 16.0-CURRENT since some hours two builders areTypically, a bunch of dependencies is waiting for llvm22 to finish, so only when that "logjam" is done, the rest will continue.
not doing anything any more:
root@jet:~ # poudriere status -b
Queued: 516 Inspected: 0 Ignored: 0 Built: 170 Failed: 3 Skipped: 1 Fetched: 0 Remaining: 342[160-CURRENT-ports20261023] [2026-10-24_21h14m23s] [parallel_build] Time: 16:40:56
ID TOTAL ORIGIN PKGNAME PHASE TIME TMPFS CPU% MEM%
[03] 16:36:43 devel/llvm22@default | llvm22-22.1.8_1 build 16:32:13 131.8% 5.5%
[04] 03:20:59 editors/libreoffice | libreoffice-26.8.1.1 build 03:11:05 146.6% 5.6%
Logs: /usr/local/poudriere/data/logs/bulk/160-CURRENT-ports20261023/2026-10-24_21h14m23s
The builder 01 and 02 finished their last port successful and did not picked up more work. Overall now 1960 of 2316 are built. The number 516 is due
to a restart last night, until the 1800 have been built fine.
I can't imagine that the remaining ports (all x11 and kde-stuff) are
waiting on devel/llvm22@default and editors/libreoffice. I will let
finish devel/llvm22@default which is now at 99% and restart then
poudriere. Any other ideas?
El d|!a domingo, octubre 25, 2026 a las 03:33:40p. m. +0100, Rainer Duffner escribi||:I usually enable the following setting in poudriere.conf: HTML_TRACK_REMAINING=yes
Am 25.10.2026 um 14:03 schrieb Dimitry Andric <dim@FreeBSD.org>:
Typically, a bunch of dependencies is waiting for llvm22 to finish, so only when that "logjam" is done, the rest will continue.
Furthermore, if it ends up building llvm22 and libreoffice simultaneously, it is likely that the host machine is going to be highly loaded, and maybe going into swap? Have you checked how much RAM and swap are used?
Over the years, RAM and swap requirements have risen significantly.
This is especially true when it happens that it's building two rCRlargerCL things at the same time. For me it was gcc14 and rust.
chromium is also notorious for requiring huge amounts of RAM and swap for linking.
After the successful end of llvm22, the other two builders picked up
ports from the queue again. So, sorry for the noise.
A way to look into the queue to see what is waiting for actual running
builds would be nice, though.
Poudriere comes with the ability to view progress via the Web (e.g.,
using Nginx or Apache). I have that set up and use it if I want to
see the current progress of a build (also to easily see build logs for
a given port). For a build, it will let you see (amongst other
things) the queued ports and the reason for their being queued.
Le dim. 25 oct. 26 |a 17:30:40 +0100, Paul Mather <paul@gromit.dlib.vt.edu> |-crivait :IIRC, ^T will show you what is currently being built on the builders, but not the ports they're holding up because they're depending upon them. (An option to "poudriere status" to list the ports waiting upon each port currently being built by each builder would be a more analogous non-browser option.)
Poudriere comes with the ability to view progress via the Web (e.g.,
using Nginx or Apache). I have that set up and use it if I want to
see the current progress of a build (also to easily see build logs for
a given port). For a build, it will let you see (amongst other
things) the queued ports and the reason for their being queued.
And if the web interface is not installed, SIGINFO (just press ^T) is
fine.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 60:46:26 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
4 files (9,632K bytes) |
| Messages: | 286,219 |