From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kalle Valo Subject: Re: [RFC][PATCH 00/31] implement atomic_fetch_$op Date: Fri, 22 Apr 2016 21:35:06 +0300 Message-ID: <874matxzj9.fsf@purkki.adurom.net> References: <20160422090413.393652501@infradead.org> <20160422094455.GO3430@twins.programming.kicks-ass.net> <20160422125656.GA15453@wfg-t540p.sh.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]:34976 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751172AbcDVSfR (ORCPT ); Fri, 22 Apr 2016 14:35:17 -0400 In-Reply-To: <20160422125656.GA15453@wfg-t540p.sh.intel.com> (Fengguang Wu's message of "Fri, 22 Apr 2016 20:56:56 +0800") Sender: linux-arch-owner@vger.kernel.org List-ID: To: Fengguang Wu Cc: Peter Zijlstra , torvalds@linux-foundation.org, mingo@kernel.org, tglx@linutronix.de, will.deacon@arm.com, paulmck@linux.vnet.ibm.com, boqun.feng@gmail.com, waiman.long@hpe.com, fweisbec@gmail.com, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, rth@twiddle.net, vgupta@synopsys.com, linux@arm.linux.org.uk, egtvedt@samfundet.no, realmz6@gmail.com, ysato@users.sourceforge.jp, rkuo@codeaurora.org, tony.luck@intel.com, geert@linux-m68k.org, james.hogan@imgtec.com, ralf@linux-mips.org, dhowells@redhat.com, jejb@parisc-linux.org, mpe@ellerman.id.au, schwidefsky@de.ibm.com, dalias@libc.org, davem@davemloft.net, cmetcalf@mellanox.com, jcmvbkbc@gmail.com, arnd@arndb.de, dbueso@suse.de Fengguang Wu writes: >> OK, weirdness. I received the "BUILD SUCCESS" email without any arm64 >> builds listed, but I just received a build bot email telling me the >> arm64 build was borked (which I know it is). > > Sorry, that may happen because even though most errors will be > detected in the first hour or before the BUILD SUCCESS/DONE > notification, the build/boot/performance tests for a particular branch > may continue for days, during the time test coverage keeps growing. > Which means it's possible to receive a build failure after receiving > BUILD SUCCESS notification. > > In particular, 0-day bot classify 500+ kconfigs into 2 priority lists: > > P1: 100+ realtime priority kconfigs which should be finished before sending > out BUILD SUCCESS notification > > P2: 400+ background priority kconfigs which may take hours to days to finish > > That split is a tradeoff between timeliness and completeness. It turns > out to work well as long as we choose the suitable P1 list. > > So the more accurate interpretation of "BUILD SUCCESS/DONE" would be: > 0day bot is working on your tree (no worry about out-of-service) and > reached a major milestone. Thanks, this is very useful information. But would it be also possible to get a report about the P2 completion (or failure)? -- Kalle Valo