[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] [PATCH] New pre-GLEP: TEST_SUITE_PRESENT variable
From:       Michał_Górny <mgorny () gentoo ! org>
Date:       2023-02-24 13:28:24
Message-ID: f4070ec2e65f6802bc293ea7b8502fc82db301a8.camel () gentoo ! org
[Download RAW message or body]

On Sun, 2023-02-19 at 18:32 +0100, Michał Górny wrote:
> +Abstract
> +========
> +
> +A new ``TEST_SUITE_PRESENT`` variable is introduced to indicate whether
> +the package features a test suite.  It can be set either by the ebuild,
> +the eclass or the default ``src_test`` implementation, and afterwards
> +included in the package manager logs.  This can aid in analyzing
> +the results of automated package testing.
> 

I've decided to withdraw this proposal.  After giving it more thought,
it doesn't really solve the problem it was intended to solve, and it is
unnecessarily complex for a non-solution.

Long story short, a package may use Python AND have a test suite, yet
not test anything actually written in Python.  The proposal would
qualify these packages as having the test suite, yet in the end it
wouldn't provide useful input for PYTHON_COMPAT testing.

I think a domain-specific solution such as checking for python_test() or
distutils_enable_tests will work better here, and other packages will
still require manual verification.

-- 
Best regards,
Michał Górny


[prev in list] [next in list] [prev in thread] [next in thread]