From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 9E2BB138350 for ; Tue, 21 Apr 2020 20:51:19 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A5777E0BD7; Tue, 21 Apr 2020 20:51:13 +0000 (UTC) Received: from mail-pf1-f172.google.com (mail-pf1-f172.google.com [209.85.210.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 542FEE0B37 for ; Tue, 21 Apr 2020 20:51:13 +0000 (UTC) Received: by mail-pf1-f172.google.com with SMTP id d184so2776816pfd.4 for ; Tue, 21 Apr 2020 13:51:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=BLTlaStRbkelrpra92VOvqsgQyntRYh5ls0xqBu1APk=; b=HChsgUny2hk49+Yn/vY1iQad4QdDZSdxMFNWzw+mY/ah2CwSK5UIZ89qpOpqil07zh 3FA8KDP9VktDnpCx5Jn3fsXnbC/7B4b+sa9h1MWBBcwPlwC6TMdgBXyla6BgT9oL5IXP rSInCSu49iTbgWqMhWYBFJyLck9GkiUn8wpZ2AbQsscXIsXyngeupxxQXV2wFjG71/dr qnFgvkgdZYB/obwLo+QwTyYBvgO3DvDAz7IcCYx78fEQHhHXVe6DfrzxT888oW7BOT0T 7HUvbk9vVPZIaN0Z/f/CC7yVt+a2Y6y3iCL1A6iGAwhRISdq1SlNhOHQiHieZkKqYf90 Z0bQ== X-Gm-Message-State: AGi0PuZZfnpqs02+vcP/9qzlhBxW4fNx4/+LNwOhxMbvPIzf7RdD3efK xWeHFKEoM4tBptQyIlxTe57+Gd1NB3lr0WFV+PZuGoxp X-Google-Smtp-Source: APiQypKTzVZ967y5/4TjAFBG0j647DrF1/D+E9DMK1leyLdveozAI/NnA+sc7QVvRqjIuDsYxOA8plAMWq1nqQek1Nk= X-Received: by 2002:a63:5657:: with SMTP id g23mr18866881pgm.224.1587502271848; Tue, 21 Apr 2020 13:51:11 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <20200421165803.GB187193@redacted> <11506562.O9o76ZdvQC@peak> <20200421190145.GF187193@redacted> In-Reply-To: From: Michael Jones Date: Tue, 21 Apr 2020 15:51:00 -0500 Message-ID: Subject: Re: [gentoo-user] Gentoo Tinderboxes? To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="000000000000fe78da05a3d32c95" X-Archives-Salt: 25091072-a66d-444d-8289-9d4d7b7fbeb6 X-Archives-Hash: 1af9539cd996bd6d4ebee70debecbc25 --000000000000fe78da05a3d32c95 Content-Type: text/plain; charset="UTF-8" On Tue, Apr 21, 2020 at 3:27 PM Rich Freeman wrote: > There are some QA/CI tools out there that have substantially improved > the quality of the distro, and most of them have started out as one > dev just creating a tinderbox or whatever and filing bugs when they > see problems. The only real downside to this is if somebody quits we > might lose these tools - but there are efforts to host them on infra > once we start to treat them as part of the core experience. When they > start out they're just one dev's random contributions and they may or > may not persist. > Speaking of tinderboxes: Is there any kind of QA tool that normal end users can contribute CPU cycles to? Given the massive combinatorial explosion of package configurations that can be installed using Gentoo, one might imagine that there's some value in simply installing programs with different USE combinations and running the self-tests for those programs. What I don't want to do is anything manual. Be it filing bugs, or testing things. But I'd be happy to run some arbitrary QA tool in a virtual machine or chroot nearly indefinitely. --000000000000fe78da05a3d32c95 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, Apr 21, 2020 at 3:27 PM Rich = Freeman <rich0@gentoo.org> wr= ote:=C2=A0
There are some QA/CI tools out there that have substantially improved
the quality of the distro, and most of them have started out as one
dev just creating a tinderbox or whatever and filing bugs when they
see problems.=C2=A0 The only real downside to this is if somebody quits we<= br> might lose these tools - but there are efforts to host them on infra
once we start to treat them as part of the core experience.=C2=A0 When they=
start out they're just one dev's random contributions and they may = or
may not persist.


Speakin= g of tinderboxes:

Is there any kind of QA tool tha= t normal end users can contribute CPU cycles to? Given the massive combinat= orial explosion of package configurations that can be installed using Gento= o, one might imagine that there's some value in simply installing progr= ams with different USE combinations and running the self-tests for those pr= ograms.

What I don't want to do is anything ma= nual. Be it filing bugs, or testing things.

But I&= #39;d be happy to run some arbitrary QA tool in a virtual machine or chroot= nearly indefinitely.
--000000000000fe78da05a3d32c95--