Solved How to tell if poudriere build is stalled?

byrnejb

byrnejb

How can I tell if the build process is stalled or not? Successive <ctrl>T yield this. This means that llvm80 has been compiling for almost an hour. Is this usual?
Code: 
load: 1.37  cmd: sh 16054 [piperd] 13692.28r 0.26u 0.73s 0% 3864k
[freebsd_12-1x64-PORTS-12-1] [2020-05-01_11h04m42s] [parallel_build:] Queued: 155 Built: 148 Failed: 0   Skipped: 0   Ignored: 0   Tobuild: 7    Time: 03:48:21
    [02]: devel/llvm80              | llvm80-8.0.1_3            build           (02:38:40 / 02:41:02)
[03:48:24] Logs: /usr/local/poudriere/data/logs/bulk/freebsd_12-1x64-PORTS-12-1/2020-05-01_11h04m42s
[03:48:24] WWW: https://vhost04.hamilton.harte-lyne.ca//build.html?mastername=freebsd_12-1x64-PORTS-12-1&build=2020-05-01_11h04m42s


load: 1.31  cmd: sh 16054 [piperd] 17208.76r 0.26u 0.73s 0% 3864k
[freebsd_12-1x64-PORTS-12-1] [2020-05-01_11h04m42s] [parallel_build:] Queued: 155 Built: 148 Failed: 0   Skipped: 0   Ignored: 0   Tobuild: 7    Time: 04:46:57
    [02]: devel/llvm80              | llvm80-8.0.1_3            build           (03:37:16 / 03:39:38)
[04:47:00] Logs: /usr/local/poudriere/data/logs/bulk/freebsd_12-1x64-PORTS-12-1/2020-05-01_11h04m42s
[04:47:00] WWW: https://vhost04.hamilton.harte-lyne.ca//build.html?mastername=freebsd_12-1x64-PORTS-12-1&build=2020-05-01_11h04m42s
 
If it reacts to Ctrl+T, it is alive and working. LLVM is huge, so expect long build times. See other threads in this forum to learn about ways for improving build times.

If you want to see exactly what's going on, you got a path to the logfiles in your poudriere output. look for the llvm80 logfile in the "logs" subdirectory of that and run e.g. tail on it.
 
I can recommend using nginx or Apache to provide a nice overview of what Poudriere is doing. You can find example configs in /usr/local/share/examples/poudriere.

poudriere.jpg
Yeah, I forgot something. Now Chromium has been busy building for the past 22 hours :oops:
 
SirDice said:
Yeah, I forgot something. Now Chromium has been busy building for the past 22 hours :oops:
Click to expand...
That's...really scary. Firefox by itself used to take ~2.5 hours on my machine but I recently enabled ALLOW_MAKE_JOBS_PACKAGES in poudriere.conf and added some more packages to it that take forever, including Firefox. It has cut the time down to ~1 hour, but it also makes my machine slow down noticeably, especially when multiple packages are using make jobs, so caveat emptor. Currently rebuilding everything with MAKE_JOBS_NUMBER specified in the make.conf that my Poudriere build will use.

Edit: And rather than ~5 hours for everything I use to build, I was going on 6 hours with Firefox just getting started (it's the last port to build on my machine, and I didn't create a separate make.conf just for CPU-intensive stuff), so I think it's safe to say that MAKE_JOBS_NUMBER in make.conf indeed works. But I'm not sure if that will be as useful as I originally thought, so nevermind that part. :)
 
You must log in or register to reply here.
Back
Top