Issue #2659 has been updated by tuxillo. Status changed from New to Closed Assignee set to dillon
Fixed in master (see associated revision) ---------------------------------------- Bug #2659: Make jobs Issue with bmake-20131001 update http://bugs.dragonflybsd.org/issues/2659#change-11912 * Author: tuxillo * Status: Closed * Priority: Normal * Assignee: dillon * Category: Build * Target version: 3.8.0 ---------------------------------------- Hi all, We have an issue with latest bmake update which was merged in commit: commit 920d8dfc4cd17a2f41f47e3e3be6ef7e963814dd Date: Sat Nov 23 12:32:57 2013 +0100 Doing a 'make -j5 buildworld' used to spawn a maximum of 5 cc1 & cc1plus processes. Whereas now, with bmake-20131001 it can spin up to 20. I've been monitoring a buildworld process with the "buggy" bmake. The output shows the number of make processes and cc1 or cc1processes (defined as ccjobs). Everytime the monitoring script detected more than 5 ccjobs, it printed 'ps axlR' command to the log, so that one can see _exactly_ what was being built. You can find the log here: http://leaf.dragonflybsd.org/~tuxillo/archive/temp/makebug_0021 Needless to say, that with previous bmake it's never spawned more than the number specified with -j (At least on my tests). Furthermore, on a system rendered unusable by a build process, I could make a coredump which I can upload for anyone that wants to deep digger if necessary. Let me know if anyone needs more details. Cheers, Antonio Huete -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account