Date: Sun, 5 Feb 2012 21:41:57 +1100 From: Jan Mikkelsen <janm-freebsd-hackers@transactionware.com> To: freebsd-hackers@freebsd.org Cc: Garrett Cooper <yanegomi@gmail.com>, Xin LI <delphij@delphij.net>, Ivan Voras <ivoras@freebsd.org>, davidxu@freebsd.org Subject: Re: sem(4) lockup in python? Message-ID: <5D37298B-9D68-4F0F-8AAB-E8F2DBB9D9C3@transactionware.com> In-Reply-To: <CAGH67wRsek2-WY_ETW6QEER1r5dDXLXfDjbzpHMjtv059Y8cJw@mail.gmail.com> References: <jejrbe$or8$1@dough.gmane.org> <201201110806.30620.jhb@freebsd.org> <CAF-QHFWFvYTPeM68Mk%2BOYVX--MNhKOJ2o1GF9ZOsBmtiC5fYFQ@mail.gmail.com> <CAGH67wRsek2-WY_ETW6QEER1r5dDXLXfDjbzpHMjtv059Y8cJw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/01/2012, at 3:47 AM, Garrett Cooper wrote: > [ builds hanging in python with waf =85 ] > Glad to see that iXsystems isn't the only one ([1] -- please add a "me > too" to the PR). The problem is that we do FreeNAS nightlies and they > frequently get stuck building tdb (10%~20% of the time) and it sticks > when doing interactive builds as well. The issue appears to be > exacerbated when we have more builds running in parallel on the same > machine. I've also run into the same issue compiling talloc because it > uses the same waf infrastructure as tdb, which was designed to "speed > things up by forcing builds to be parallelized" (It builds > kern.smp.ncpus jobs instead of -j 1). Furthermore, it seems to occur > regardless of whether or not we have the WITH_SEM enabled in python or > not (build.ix's copy of python doesn't have it enabled, but > streetfighter.ix, my system bayonetta, etc do). Any progress on this? Or a workaround? Just had another build stuck on this =85 Jan.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5D37298B-9D68-4F0F-8AAB-E8F2DBB9D9C3>