Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Won't Fix
-
5.5(EOL)
Description
$ perl ./mtr tokudb.type_varchar
|
...
|
|
|
==============================================================================
|
|
|
TEST RESULT TIME (ms) or COMMENT
|
--------------------------------------------------------------------------
|
|
|
worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
|
tokudb.type_varchar [ pass ] 410
|
--------------------------------------------------------------------------
|
The servers were restarted 0 times
|
Spent 0.410 of 7 seconds executing testcases
|
|
|
Completed: All 1 tests were successful.
|
|
|
elenst@wheezy-64:~/git/5.5/mysql-test$ ls var/mysqld.1/data/
|
aria_log.00000001 mysql _test_t3_status_1a5_1_1b.tokudb __tokudb_lock_dont_delete_me_environment tokudb.rollback
|
aria_log_control performance_schema tokudb.directory __tokudb_lock_dont_delete_me_logs
|
log000000000000.tokulog27 test tokudb.environment __tokudb_lock_dont_delete_me_recovery
|
mtr _test_t3_main_1a5_2_1b.tokudb __tokudb_lock_dont_delete_me_data __tokudb_lock_dont_delete_me_temp
|
Any further test that attempts to create t3 (not necessarily of TokuDB engine), fails with 'table already exists').
It's not MariaDB-specific, same happens on Tokutek release binaries of MySQL 5.5.41.
Attachments
Issue Links
- relates to
-
MDEV-7069 Fix buildbot failures in main server trees
-
- Stalled
-
- links to
