[MDEV-13405] Some TokuDB MTR tests are impossible to run by name Created: 2017-07-30  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 5.5, 10.0, 10.1, 10.2
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Elena Stepanova
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

$ perl ./mtr tokudb.lockretry-writelocktable.insert
...
Collecting tests...
mysql-test-run: *** ERROR: Illegal format of test name: tokudb.lockretry-writelocktable.insert

The reason is that mtr_cases.pm expects only one dot at most in the test name.



 Comments   
Comment by Sergei Golubchik [ 2017-08-02 ]

Also, test suites in the original tokudb (from tokutek and now from percona) have dots in the name, so I was renaming them during the merge. If you want to fix mtr instead, we could rename suites back and have a bit simple tokudb merge afterwards.

Comment by Elena Stepanova [ 2017-08-05 ]

I would like to fix it in MTR, yes, but if we want to allow dots both in suite names and test names, there will always be an ambiguity – like, in tokudb.backup.backup_master_info, should it be suite=tokudb test=backup.backup_master_info or suite=tokudb.backup test=backup_master_info?

Strangely, it still doesn't seem to work in Percona server, on some other reason, even though they allow more dots in the names than we do. I'm not sure how they deal with that internally.

But on top of the dot problem, our version of MTR also cannot manage dashes in the suite name, apparently because it expects the part after the dash to indicate an overlay.

Generated at Thu Feb 08 08:05:21 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.