Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [build-check] scripts: add check_build script
To:     Andrew Morton <akpm@linux-foundation.org>,
        Norbert Manthey <nmanthey@amazon.de>
Cc:     Linus Torvalds <torvalds@linux-foundation.org>,
        David Woodhouse <dwmw@amazon.co.uk>,
        linux-kernel@vger.kernel.org
References: <1530186789-28808-1-git-send-email-nmanthey@amazon.de>
 <1530623539-650-1-git-send-email-nmanthey@amazon.de>
 <20180703154914.5d3e8f28e1d87e48180073e3@linux-foundation.org>
From:   Randy Dunlap <rdunlap@infradead.org>
Message-ID: <01151c44-c3f7-c344-8e58-2e6b348960fb@infradead.org>
Date:   Tue, 3 Jul 2018 16:27:06 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <20180703154914.5d3e8f28e1d87e48180073e3@linux-foundation.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 07/03/2018 03:49 PM, Andrew Morton wrote:
> On Tue, 3 Jul 2018 15:12:10 +0200 Norbert Manthey <nmanthey@amazon.de> wrote:
> 
>> This script performs build testing, by building several configurations
>> several times. The script is introduced to improve the consistency of
>> testing changes in the kernel configuration.
>>
>> This version build randconfig 10 times, as well as allyesconfig,
>> allnoconfig and allmodconfig. Depending on the used machine and system
>> setup, the script might take a while to finish.
>>
>> The script logs all the used config files, as well as the output of the
>> build commands to a log directory "build_check_logs", so that this data
>> can be retrieved after running the script.
> 
> I'm unable to even guess how many people will find this useful.

I expect that lots of us have similar scripts.

>> +build ()
>> +{
>> +	local -r LOG_FILE="$1"
>> +	local -i STATUS=0
>> +
>> +	make clean -j $(nproc) &> /dev/null
>> +	make -j $(nproc) &>> "$LOG_FILE" || STATUS=$?
>> +
>> +	echo "build status: $STATUS" >> "$LOG_FILE"
>> +	echo "[$SECONDS] build status: $STATUS"
>> +	return "$STATUS"
>> +}
> 
> The script never sets nproc.  So I guess this is a bare `make -j'. 
> When I type that on my (quite beefy) workstation I get eleventy xillion
> processes and the machine locks up.  Can't even wiggle the mouse. 
> After a 20 minute nap (thanks!) it was still comatose so I hit the big
> button (who writes this junk??).
> 
> So you might want to take an educated guess from /proc/cpuinfo here.

or use
nproc=`getconf _NPROCESSORS_ONLN`

or double it if you want to keep processes ready/waiting.

-- 
~Randy