From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (unknown [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 6BDD71381FA for ; Sat, 10 May 2014 00:28:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 75C9FE096B; Sat, 10 May 2014 00:28:21 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D81D2E0960 for ; Sat, 10 May 2014 00:28:20 +0000 (UTC) Received: from localhost.localnet (unknown [114.91.164.8]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: patrick) by smtp.gentoo.org (Postfix) with ESMTPSA id 6C97F335DE7 for ; Sat, 10 May 2014 00:28:18 +0000 (UTC) From: Patrick Lauer To: gentoo-project@lists.gentoo.org Subject: [gentoo-project] Tinderbox and building everything Date: Sat, 10 May 2014 08:28:14 +0800 Message-ID: <2494968.RL10ZYJ7qd@localhost> User-Agent: KMail/4.13 (Linux/3.13.1-gentoo; KDE/4.13.0; x86_64; ; ) In-Reply-To: <536D13CF.2000403@gentoo.org> References: <20140509172925.29e3f212@gentoo.org> <536D13CF.2000403@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Archives-Salt: 698b615b-6e62-445d-bbfb-773f585f6cd1 X-Archives-Hash: bc63602fa0b469da15447cca29b37696 On Friday 09 May 2014 17:43:43 hasufell wrote: > I used to believe it's lack of manpower/time or even laziness, but I am > not sure anymore. > > blah blah tinderbox So, as someone who has done lots of package building in the past ... My actual "tinderbox" was 12 lines of bash, split over two files. It's absolutely not a technical problem. On my old hardware (dualcore amd64) I generated about 1k package build logs a day, with my current hardware that should easily be 5k logfiles. Now the "building" part is relatively boring, but now you have the logfiles, you should do something with them. My heuristic was to grep for "Error:" at the beginning of a line, that was unique enough that I only saw two false positives so far. On a good day that was about 150 files to process. (There's some interesting setup issues that you'll encounter, but most of those can be scripted away, e.g. some packages need kernel sources -> emerge gentoo-sources; cd /usr/src/linux; make defconfig modules_prepare ) With an optimized workflow I could get my processing time to around one minute per logfile on average, my personal best was filing 160 bugs in 90 minutes. This is a lot of tedious work - and I stopped doing it once Flameeyes was doing the same and we had about 90% "the same" bugs, thus making my work redundant enough that it wasn't worth the time. THAT is the bottleneck - getting people motivated to triage logs (which can be automated quite far) and file bugs (which is demotivating and exhausting). You fix that problem and the rest is easy ... If you expect this to happen in any reasonable way ... either pay me to do it (I have the experience, but not the time), motivate others (hahaha), or do it yourself. Have fun, Patrick