In my environment, I have a designated "build machine" (named "freebeast"); in addition to building FreeBSD for itself and a couple of other machines, it also builds packages (via devel/poudriere-devel) for those other machines. (Each machine is amd64, running stable/12.)
The other machines get weekly updates (every Sunday), so I set up freebeast to build the bulk of the packages every Saturday, then (usually) the Sunday set of packages to build is relatively small (so I can get the weekly updates done faster than if I were to wait until Sunday to build all the packages that warrant rebuilding). Details are in http://www.catwhisker.org/~david/FreeBSD/upgrade.html. Today, after building stable/12 & head, I set freebeast to building packages; a while later, Spouse and I took the tandem bike out for a ride (for about 2.5 hours). A whlie later, I noticed that freebeast was still chugging away; ^T revealed that it was building www/chromium (which was expected); it also revealed that there had been a failure (which was not): load: 8.59 cmd: sh 99503 [piperd] 35609.83r 1.23u 1.88s 0% 2156k [12amd64-ports-home] [2020-05-23_12h08m48s] [parallel_build:] Queued: 1003 Built: 999 Failed: 1 Skipped: 2 Ignored: 0 Tobuild: 1 Time: 09:53:48 [05]: www/chromium | chromium-81.0.4044.138_1 build (03:59:48 / 04:08:53) [09:53:49] Logs: /tank/poudriere/poudriere/data/logs/bulk/12amd64-ports-home/2020-05-23_12h08m48s A quick check revealed that lang/rust was the failing port; I've dumped a copy of the poudriere log (there's a gzipped copy there, as well) and an "info.txt" file that shows things like "uname -a" output from freebeast, as well as information about ports-mgmt/poudriere-devel and the current state of the SVN working copies for src & ports. It appears (to my eye that is quite unfamiliar with rust) that the first failure in the log is: sysroot: "/wrkdirs/usr/ports/lang/rust/work/rustc-1.43.1-src/build/x86_64-unknown-freebsd/stage1" libdir: "/wrkdirs/usr/ports/lang/rust/work/rustc-1.43.1-src/build/x86_64-unknown-freebsd/stage1/lib" error: could not compile `rustc_lint`. (which shows up quite near the end of the supplied log file). Please note that the machine has been building www/firefox (and thus, lang/rust) routinely for quite some time, so this is a little surprising. Even more surprising is that my laptop, where I also have www/firefox installed, and which I update via ports-mgmt/portmaster, has rust-1.43.1 built and installed, apparently without issue (other than consuming time and generating heat). I expect that once www/chromium finally finishes, I'll give poudriere another chance at the "stragglers" (and record the results in http://www.catwhisker.org/~david/FreeBSD/ports/rust/). Peace, david -- David H. Wolfskill da...@catwhisker.org "The Liar Tweets Tonight": https://www.youtube.com/watch?v=TkU1ob_lHCw See http://www.catwhisker.org/~david/publickey.gpg for my public key.
signature.asc
Description: PGP signature
