On Sat, 11 Jan 2020 at 21:38, Greg Troxel <g...@lexort.com> wrote: > > Manuel Bouyer <bou...@antioche.eu.org> writes: > > > On Sat, Jan 11, 2020 at 03:43:58PM +0100, Rhialto wrote: > >> On Fri 10 Jan 2020 at 10:25:13 -0500, Greg Troxel wrote: > >> > So maybe I've been lucky. Maybe it's MAKE_JOBS. Maybe it's something > >> > else we don't understand. > >> > >> On my machine, rust and firefox also "just built". I did get messages in > >> my xconsole windown about random though, but not only during these > >> builds it seems. > > > > I forced MAKE_JOBS=1 for rust on the build cluster, and rust did > > build on 8.0/i386 this time. A parallelism issue is coherent with the > > error message from the previous run (trying to access a non-existent file > > in the build directory) > > So I guess we have a proposal on the table that says: > > rust is broken for -jN > therefore we should set MAKE_JOBS_SAFE=no
I used to run with higher -jN many months ago and occasionally hit rust build problems. Since I - by necessity, very hot laptop - switched to -j1, I don't think I've had a failure; a few days ago I built rust 1.40. > > any other data points? -- ----
