From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 1E8501381F3 for ; Sun, 15 Sep 2013 19:51:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A1491E0BFF; Sun, 15 Sep 2013 19:51:39 +0000 (UTC) Received: from smtprelay05.ispgateway.de (smtprelay05.ispgateway.de [80.67.31.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1395BE0BFF for ; Sun, 15 Sep 2013 19:51:39 +0000 (UTC) Received: from [85.179.1.76] (helo=[192.168.1.2]) by smtprelay05.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1VLIM5-00086i-0l for gentoo-releng@lists.gentoo.org; Sun, 15 Sep 2013 21:51:37 +0200 Message-ID: <52360FE4.7030000@gentoo.org> Date: Sun, 15 Sep 2013 21:52:04 +0200 From: Sebastian Pipping User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130829 Thunderbird/17.0.8 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-releng@lists.gentoo.org Reply-to: gentoo-releng@lists.gentoo.org MIME-Version: 1.0 To: gentoo-releng@lists.gentoo.org Subject: Re: [gentoo-releng] Autobuilds go to /experimental and to /releases only when someone actually tests them? References: In-Reply-To: X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Df-Sender: c3BpbmctZ2VudG9vQGJpbmVyYS5kZQ== X-Archives-Salt: 36222541-962a-4de2-83de-b1618a67ae6f X-Archives-Hash: 0a4b99cabfb576a0a6cfe6f95bca036f On 29.07.2013 22:38, Matt Turner wrote: >> The alternative here is the automated testing that I've talked about with >> others on FOSDEM and Prague last year, but that still needs to be done. >> Amongst other testing, the idea would be to pick the latest ISO and boot it >> on some virtualization platform and catch the console output to ensure it >> booted successfully and not tests failed. > > Some recent problems have involved linux-firmware being broken. I > don't think virtualization will help notice that, e.g., the Tigon 3 > firmware is missing. Ideally, you'd use virtualization and some concrete physical platforms in parallel. For virtualization, KVM Qemu might be quick to get results, I think I used something like -append 'earlyprintk=serial,keep' -serial file:/abs/path/log/file previously to log the full console output from inside a KVM machine. That could be the base of a regression test suite. Best, Sebastian