Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Hi,
we have a nice tiny feature in Fedora and RHEL, I want to share with other distros.
When we solve some troubles with tests, we list them with comments to a standalone file. Then, we add '--skip-test-list' option, to the testsuite.
It help us quickly enable / disable test in 'developement' time, and use different lists for different architectures.
The code is already in place, I only offer a better documentation and a suggestions to ship that file ( mysql-test/skipped-tests.list ) by default (even if it would be empty - since you disable / enable tests directly in each test file)
Take a glimpse at the attachement. It is a patch we use and it is written for Red Hat, but adding macros to the paths should solve it.
Take a look and tell me, what you think.
I don't know how others, but RPM distros - like SUSE - could look into Fedora specfile and ease their maintainers lifes with this
Actually, we already have the file itself in 10.0/10.1, it's called unstable-tests, and it's far from empty. The file is used when a reliable subset of tests is needed (e.g. when tests are a part of the build process), to avoid sporadic and irrelevant failures. Naturally, something can always be added to it based on distribution or architecture specifics (it is also known to happen).
The list is updated before every release. It uses pessimistic approach – tests are unstable unless are proven to be stable enough. Basic rules for the list are these:
For 10.2 it is not maintained yet, but it will be by the time 10.2 goes GA.
Inclusion:
Exclusion:
On an additional note, if you are want to enable/disable tests really quickly, depending on your process, it might be easier to use --skip-test rather than --skip-test-list.