• Re: poudriere-devel: only 2 builder of 4 are running

    From Dimitry Andric@dim@FreeBSD.org to muc.lists.freebsd.ports on Sun Oct 25 14:03:23 2026
    From Newsgroup: muc.lists.freebsd.ports

    On 25 Oct 2026, at 13:08, Matthias Apitz <guru@unixarea.de> wrote:


    While building ports on 16.0-CURRENT since some hours two builders are
    not doing anything any more:

    root@jet:~ # poudriere status -b
    [160-CURRENT-ports20261023] [2026-10-24_21h14m23s] [parallel_build] Time: 16:40:56
    Queued: 516 Inspected: 0 Ignored: 0 Built: 170 Failed: 3 Skipped: 1 Fetched: 0 Remaining: 342
    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?
    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?
    -Dimitry
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Dimitry Andric@dim@FreeBSD.org to muc.lists.freebsd.ports on Sun Oct 25 16:29:08 2026
    From Newsgroup: muc.lists.freebsd.ports

    On 25 Oct 2026, at 16:01, Matthias Apitz <guru@unixarea.de> wrote:

    El d|!a domingo, octubre 25, 2026 a las 03:33:40p. m. +0100, Rainer Duffner escribi||:

    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.
    I usually enable the following setting in poudriere.conf: HTML_TRACK_REMAINING=yes
    The comment in poudriere.conf says that it might lead to a slight slowdown, but I find it very handy to see which ports are still pending.
    -Dimitry--
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thierry Thomas@thierry@freebsd.org to muc.lists.freebsd.ports on Sun Oct 25 18:18:15 2026
    From Newsgroup: muc.lists.freebsd.ports

    --qr3zxsH8uOzkbHG2
    Content-Type: text/plain; charset=iso-8859-1
    Content-Disposition: inline
    Content-Transfer-Encoding: quoted-printable

    Le dim. 25 oct. 26 =E0 17:30:40 +0100, Paul Mather <paul@gromit.dlib.vt.edu>
    =E9crivait=A0:

    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.

    Regards,
    --=20
    Th. Thomas.

    --qr3zxsH8uOzkbHG2
    Content-Type: application/pgp-signature; name=signature.asc

    -----BEGIN PGP SIGNATURE-----

    iQJPBAEBCAA5FiEE5Ta+hThTmdALb6p28cUWs8g1l1MFAmreOcsbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMiwzAAoJEPHFFrPINZdT5lQP/RmtbnHzWXg8GPSDdEZD SNShf//dHLZV6XvdWSUVSIo0Qouhj3dUfa1vbQ8S1hqFGxm7P3DBxCxtvpmyUD6W AKvN5j+5LpsmtnelWX1vpI2A5CXTRibgc1pSUEoDwd4PKwyl+Eeu6tBItD8slShz jn+D+ts05JUGXUObc4ugoB5d6ZQEOEv2KfPxubGlEbPkd5OSB4bwvG2cHCzrgH15 qmnDbfGmk3wh5KHHV834vubwnZdXjpNSlfKFwSB87aiXC83fTG1Tg1Bfaz8TfAl1 m1I3p/I1msxFETjIRiqRGiEOv5Tt/hjq100lBnKMNuWjfmwR9rIt/3XJD0pMW4eZ 7Xqw3Joa+XHFfWpL4o+U2KzOhXmV8cs8b8FCTAce1OvnygahQ4xe+vfG6gozOHw7 pfaOyYWejZGdhHF5fVfWpnX8u5kW9ICma11fqJLY1Pc7jiaOcGtQT8GwzL0i5Nl/ p7T61l3unPqwa1AkMCaLEItn1Br9UqXpUpMlgwETSI29cYYJBUfDe8MoSfdiY+Cn iAesbYd9ebQPQWR9EJ7bS4GvEzba6P41wyP0lEBVxDwg5pojfB2EHeZdagwZJ8nh b2Ty5jHfzXjNZY3Thp+UrpYzQZDvlfknc9R7LJDtITH9edsUIquYvbI0SP89wW76 lkt9UCr939SBmvWdZ02P6Jow
    =WsaC
    -----END PGP SIGNATURE-----

    --qr3zxsH8uOzkbHG2--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Mather@paul@gromit.dlib.vt.edu to muc.lists.freebsd.ports on Sun Oct 25 13:28:49 2026
    From Newsgroup: muc.lists.freebsd.ports

    On Oct 25, 2026, at 1:18rC>pm, Thierry Thomas <thierry@freebsd.org> wrote:
    Le dim. 25 oct. 26 |a 17:30:40 +0100, Paul Mather <paul@gromit.dlib.vt.edu> |-crivait :

    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.
    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.)
    Cheers,
    Paul.
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2