Date: Tue, 13 Feb 2018 18:37:24 -0800 (PST) From: Don Lewis <truckman@FreeBSD.org> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> Cc: Joerg Sonnenberger <joerg@bec.de>, freebsd-hackers@freebsd.org Subject: Re: rare gmake jobserver hangs, lost SIGCHLD? Message-ID: <tkrat.4501d0b68816853f@FreeBSD.org> In-Reply-To: <201802132323.w1DNNv93050851@pdx.rh.CN85.dnsmgr.net> References: <20180213221838.GA7424@britannica.bec.de> <201802132323.w1DNNv93050851@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13 Feb, Rodney W. Grimes wrote: >> On Tue, Feb 13, 2018 at 10:46:32AM -0800, Don Lewis wrote: >> > Starting in December 2016, I've seen three build runaway failures on >> > different ports. >> >> https://savannah.gnu.org/bugs/?49014 might be your problem. > > And given you said Ryzen earlier there is also this issue just found > and fixed: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 Yes, I tested that patch and found that it got rid of several different semi-random port build failures. I just happened to get this gmake-related build runaway on my first poudriere run after applying the VM patch.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?tkrat.4501d0b68816853f>