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:

• tests which have failed in buildbot in the corresponding branch since the previous release go to the list (and bug reports are created for them);
• tests for which we have open bug reports remain on the list until the bug reports are closed;
• tests which have been added or modified since the previous release, directly or via include files, go to the list (trivial modifications can be ignored on case by case basis).

Exclusion:

• tests for which we do not have open bugs and which have not been modified and have not failed since the previous release (sometimes over two release cycles, depending on their length) are excluded from the list.

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.

Great!
That is good to know.
I changed Fedora's package to use the "unstable-tests" lists instead, while extending the list with ours.

However, I still believe, the comment in the patch should be reviewed.
After changing certain words about Red Hat implementation, I believe, it better describe how to run the testsuite, what basic option you have and why you need to run it on local server.

https://github.com/MariaDB/server/commit/9b897d663a116c5484dade0404870975fd5a2e68

I've added suggested notes with some changes, and while at that, have also done other modifications.

mschorm, I delayed this simple request a lot, sorry about that. Please check the RedHat-related part, if it's already become outdated, I will fix it further.

Actually, beacuse this discussion, I removed the mentioned 'rh-skipped-tests.list' and all RH tests, that I want to skip are now appended to the 'unstable-tests' file - as it should be.
So you can drop the mentions of that file.

The important part is about "How to run the testsuite at RH family OSs".

Thanks. I've removed the mention of rh-skipped-tests.list.