public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] QA obscurity: "hasq test $FEATURES" != "use test"
Date: Wed, 22 Jul 2009 13:45:38 -0700	[thread overview]
Message-ID: <robbat2-20090722T203313-158614789Z@orbis-terrarum.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

So I saw the recent set of bugs filed for QA, complaining about misuse
of FEATURES, specifically that we should not be using the FEATURES
variable, and instead should be using "use test" to check for tests
being enabled.

USE=test means: "build with support for tests"
FEATURES=test means: "actually run the tests"

So consider:
FEATURES=-test USE=test emerge ...
This would build the testsuite, and depending on the package, install
the tests the system, but NOT run them in src_test.

In the packages, I'd like to know:
1. From any phase, is src_test scheduled to be run? (FEATURES=test).
2. Has src_test run yet?

For iasl, upstream requests that if the tests are run at build time,
that they are installed to the system, which is what we do. If
FEATURES=-test USE=test is used however, using 'use test' is bogus,
because I cannot detect that the tests are going to/have run.

-- 
Robin Hugh Johnson
Gentoo Linux Developer & Infra Guy
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 330 bytes --]

             reply	other threads:[~2009-07-22 20:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22 20:45 Robin H. Johnson [this message]
2009-07-22 20:50 ` [gentoo-dev] QA obscurity: "hasq test $FEATURES" != "use test" Ciaran McCreesh
2009-07-22 21:38 ` Zac Medico

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=robbat2-20090722T203313-158614789Z@orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox