Date: Wed, 22 Mar 2017 09:49:08 -0700
From: Bryan Drewery <bdrewery@FreeBSD.org>
To: Naram Qashat <cyberbotx@cyberbotx.com>
Cc: freebsd-ports@FreeBSD.org
Subject: Re: poudriere 3.1.15 and 3.1.16 builders get stuck in {balancing,clean}_pool status
Message-ID: <2ec6d6b1-6eff-fb07-8b82-88c2648a8517@FreeBSD.org>
In-Reply-To: <532f0b3ec81a14a08b3afc7265450795@cyberbotx.com>
References: <532f0b3ec81a14a08b3afc7265450795@cyberbotx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--FAsAEpXEAIAq92lmTLtqe0U88gsJETQTH
Content-Type: multipart/mixed; boundary="L87dntI7Pb9mi7NjVuKTMSxdE0L7UvRCu";
protected-headers="v1"
From: Bryan Drewery <bdrewery@FreeBSD.org>
To: Naram Qashat <cyberbotx@cyberbotx.com>
Cc: freebsd-ports@FreeBSD.org
Message-ID: <2ec6d6b1-6eff-fb07-8b82-88c2648a8517@FreeBSD.org>
Subject: Re: poudriere 3.1.15 and 3.1.16 builders get stuck in
{balancing,clean}_pool status
References: <532f0b3ec81a14a08b3afc7265450795@cyberbotx.com>
In-Reply-To: <532f0b3ec81a14a08b3afc7265450795@cyberbotx.com>
--L87dntI7Pb9mi7NjVuKTMSxdE0L7UvRCu
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
On 3/22/2017 9:45 AM, Naram Qashat wrote:
> I have been transitioning to using poudriere to build ports for my
> system with custom options. Everything has been working well until I
> updated poudriere to 3.1.15 and then later 3.1.16.
Thanks for your great report and sorry for the trouble!
>=20
> My host is running FreeBSD 11.0-RELEASE-p8 amd64, and the poudriere jai=
l
> is running the same version (using the /usr/src / /usr/obj from the
> host). The host has a 6-core Intel i7 (so FreeBSD treats this at 12 CPU=
> cores).
>=20
> When I start a bulk build, I notice that sometimes, after a port has
> finished building, the status of a builder will go to balancing_pool or=
> clean_pool instead of idle. Some of the ports that were built will then=
> show up as failed AND built, with the error in the failed section
> showing a phase of balancing_pool and the build log showing "Build
> crashed: balancing_pool" near the very end. Eventually it gets to a
> state where poudriere no longer continues building ports, with all the
> builders in either the balancing_pool status or clean_pool status.
>=20
> I noticed this originally with poudriere 3.1.15 when attempting to just=
> bulk build poudriere alone (to get 3.1.16), but at that time I didn't
> notice what state the builder was in before I killed the bulk build. I
> had to update poudriere by building from the port's directory directly.=
> Then when I was on poudriere 3.1.16 and started a brand new bulk build,=
> that is when I noticed the balancing_pool and clean_pool statuses.
>=20
> This doesn't happen if I downgrade back to poudriere 3.1.14 (using
> portdowngrade to grab a copy of the port from before 3.1.15).
>=20
> The relevant changes in my poudriere.conf from the sample version:
>=20
> * Not using ZFS (NO_ZFS=3Dyes)
> * Using portlint (USE_PORTLINT=3Dyes)
> * CHECK_CHANGED_OPTIONS set to verbose
> * CHECK_CHANGED_DEPS set to yes
> * Setting a PKG_REPO_SIGNING_KEY to use the packages built by poudriere=
> through pkg
> * Only using 4 builders instead of the default 12 (PARALLEL_JOBS=3D4)
> * Save failed WRKDIRs (SAVE_WRKDIR=3Dyes)
> * Only allowing MAKE_JOBS on chromium, clang* and llvm*
> (ALLOW_MAKE_JOBS_PACKAGES=3D"chromium clang* llvm*")
> * Timestamp my logs (TIMESTAMP_LOGS=3Dyes)
This is the problem here, TIMESTAMP_LOGS=3Dyes. Set it to no for now.
A fix is ready for release in 3.1.17. I am just waiting on some other
things and more time before releasing 3.1.17.
If you depend on this functionality the patch to fix it is:
https://people.freebsd.org/~bdrewery/patches/timestamp-exit-on-eof.diff
>=20
> I believe I created the poudriere setup with 3.1.14 or maybe even
> 3.1.13. (It was only created within the last couple weeks.)
>=20
> If more information is needed to diagnose this, please let me know.
>=20
> Thanks,
> Naram Qashat
--=20
Regards,
Bryan Drewery
--L87dntI7Pb9mi7NjVuKTMSxdE0L7UvRCu--
--FAsAEpXEAIAq92lmTLtqe0U88gsJETQTH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBAgAGBQJY0qsEAAoJEDXXcbtuRpfPTE0H/0Fo6nBPV9+98f9yFq0dcjXL
ePUYlOOw9BJw2lUn1OptOZUN81kCZf+LHbZbVO7tDmMapDroRTSnNItZZusO/pUE
HX5G2IrL7ab1GHch+qGFSA+wEbYSZCr2unU1x2ku2eH2UbuW5kMmAb+S6bhi106f
MN1bx9WIub7ommJnfiBZ5FW14h57A+HsLTH4U8aA4iFMj1EGcxSOWkQyI4rGMFFp
HHeXTEs1YuFUtyZen6+VFD+R7n0qiGhRJSMV+G4DMeoQJa4cTfj0F7Wb1NmMYC9b
pX5WbhfKQoSYNMrIcPt14/BXGXrw2S+Vv1diV1SD6w0B2jkBr3lFA3lnlC/raHM=
=1519
-----END PGP SIGNATURE-----
--FAsAEpXEAIAq92lmTLtqe0U88gsJETQTH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2ec6d6b1-6eff-fb07-8b82-88c2648a8517>