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 6C6D7138262 for ; Tue, 17 May 2016 10:57:51 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E6F4F141A1; Tue, 17 May 2016 10:57:43 +0000 (UTC) Received: from mail-io0-f196.google.com (mail-io0-f196.google.com [209.85.223.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D995E224044 for ; Tue, 17 May 2016 10:57:42 +0000 (UTC) Received: by mail-io0-f196.google.com with SMTP id d62so2568703iof.1 for ; Tue, 17 May 2016 03:57:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to; bh=SFuvYxV8zfR0QDzDqTnUEINytTYSYtRxXRGh5J+vz3Y=; b=w03HGmHE5Dux9NUFkprcX6pLcNlhR4YFNYVAGg7UHHhX/cDN2Gfbu8ybb5WVoYSz6c RrGudCw8jigH48RBU8HiTOvbjAI3HTFs/kzz6ASnbqE6iF14OnQMwZ2trPZfz02cGLcE GHMbrk/nkP+sFArUkRl2054eEvtGGUhkrWp9hPHA0kGJgTvgG8nJmLMfrrl/iyEdg6FI /crF6vyGb+Of7HsW5zNKjfLcgSm/tVHX47PlVgKDyNhHMDMpPNny85uvEQPNmwpK4GVH IwYHt/kCQXK82k5lSRePORsWuruEAgZgt6ZK/3zTbR/fmtHmr5KEdAPLAnCdmUID8Cfr OyJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to; bh=SFuvYxV8zfR0QDzDqTnUEINytTYSYtRxXRGh5J+vz3Y=; b=ijJNdUkVuoVaSgsl67o4nOT93Tig+sKSZkGSRt9f8uOUsrhsHVo07mb4uTEJDCjohM w65+C0fgtKKxvR9ssBauBjVg5/WFmK60m66UsiNOB/2fusC2Hf8SGxuAmuT2Sgn5eH46 gpuE5QyRlL+9zy+awVT6zV3mH/xIb6sLt4Z6KT1+f3YSA16bUWlBXqhjbnmr9PZ4YijY GTW94SdFJj0Yfpvs2ReS8dKAGLxFaY7ZlUgVWWDi1ZA7luDCpD3ncJh6gLl5WPozeCGl UwKB4JljBwfmt8ZX+B7PSMpYHSp0+vVJtr1aMZeORRwO2VT30r9gJCvksUlq8koeIERx yZQw== X-Gm-Message-State: AOPr4FW8FF21gSkvUdn4hqhXbR74Q/Yzgy/c7EE1Xd96OmF7LpctNoEa2ojZCg8HaQlwbIX/ByqQt7nEgGwSEg== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.36.20.206 with SMTP id 197mr390330itg.24.1463482662012; Tue, 17 May 2016 03:57:42 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.64.159.8 with HTTP; Tue, 17 May 2016 03:57:41 -0700 (PDT) In-Reply-To: References: <20160516183840.4b241463@gentp.lnet> <20160517084643.GA24972@skade.schwarzvogel.de> Date: Tue, 17 May 2016 06:57:41 -0400 X-Google-Sender-Auth: AKDi_QU7idDMNp87RW1ZsNpkWq4 Message-ID: Subject: Re: [gentoo-dev] Proposal for changes for the next EAPI version From: Rich Freeman To: gentoo-dev Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 95757f30-412b-46ef-a55f-ef2875e734ec X-Archives-Hash: a46eb73ac9ad10de2cd0d43a9814e1eb On Tue, May 17, 2016 at 5:15 AM, Kent Fredric wrote: > On 17 May 2016 at 20:46, Tobias Klausmann wrote: >> And as for my pet peeve, tests that are known to fail, can we >> also annotate that somehow so I don't waste hours running a test >> suite that gives zero signal on whether I should add the stable >> keyword? Even a one-line hin in the stabilization request would >> be nice. As it is, I keep a list of known-to-fail packages and my >> testing machinery tells me to not bother with FEATURES=test in >> those case. > > IMO: Tests that are "expected to fail" should be killed. > That makes sense, though ironically the only specific hypothetical use case to come up so far was an example of just this situation. A package is broken in stable, and a test was proposed to detect if future stable candidates fix the flaw. There would be no point in delaying stabilization of a package that contains the same error as the current stable version. I don't see any harm in adding support for automated Gentoo-specific tests, but I am skeptical of how much use they'll actually get. After all, we started off with the statement that this is for situations where upstream doesn't provide test suites, and if upstream can't be bothered, why would we expect a distro maintainer to care more? -- Rich