In rare cases, both listener and worker can do poll at the same time
(one of them will return events, another one no events)
Fix test query to account for it.
This are filed as issues so I trust these will not be forgotten:
- MDEV-20372
- MDEV-21965
- MDEV-21968
- MDEV-22119
Having these tests fail the MTR permanently decreases the overall quality
of the software as:
- developers start neglecting the results from CI systems and do not spot
the new regressions their changes introduce
- reviews take many hours as a diligent reviewer needs to open all build
logs that are failing, see what is failing, and check if those are new
failures or not – alternatively reviewers stop looking at CI altogether
It is better to disable these test now and prioritize the MDEVs for the
test failure bugs than keep the MTR red and allow more test failures to
creep in.
Ubuntu Bionic 18.04 LTS will be around until 2023 while Xenial is only to
2021. Thus Bionic is much more suitable as the Travis-CI default build
environment for the 10.5 branch.
For now, still keep one Xenial build to ensure backwards compatibility.
Disable main.udf test until MDEV-21976 is addressed.
The test innodb_fts.fulltext_table_evict was only creating 1000 tables
with fulltext indexes, only to check that no tables with fulltext
indexes are being evicted.
The reason why tables containing fulltext indexes cannot be evicted is
that fts_optimize_init() invokes dict_table_prevent_eviction().
Remove the test, because it easily fails with a result difference.
Analysis by Thirunarayanan Balathandayuthapani:
By default, innodb_encrypt_tables=0.
1) Test case creates 100 tables in innodb_encrypt_1.
2) creates another 100 unencrypted tables (encryption=off) in innodb_encrypt_2
3) creates another 100 encrypted tables (encryption=on) in innodb_encrypt_3
4) enabling innodb_encrypt_tables=1 and checking that only
100 encrypted tables exist. (already we have 100 in dictionary)
5) opening all tables again (no idea why)
6) After that, set innodb_encrypt_tables=0 and wait for 100 tables
to be decrypted (already we have 100 unencrypted tables)
7) dropping all databases
Sporadic failure happens because after step 4, it could encrypt the
normal table too, because innodb_encryption_threads=4.
This test was added in MDEV-9931, which was about InnoDB startup being
slow due to all .ibd files being opened. There have been a number of
later fixes to this problem. Currently the latest one is
commit cad56fbaba, in which some tests
(in particular the test innodb.alter_kill) could fail if all InnoDB
.ibd files are read during startup. That could make this test redundant.
Let us remove the test, because it is big, slow, unreliable, and
does not seem to reliably catch the problem that all files are being
read on InnoDB startup.
The list was created based on 10.2.15 list, with the addition
of failures and modifications which happened during the last week
before the tentative 10.3.7 release commit
