[MDEV-6140] storage_engine.xa_recovery fails sporadically with "Server failed to dissapear" on server restart Created: 2014-04-20  Updated: 2018-07-19  Resolved: 2018-07-19

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 5.5.37
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Elena Stepanova
Resolution: Cannot Reproduce Votes: 0
Labels: tests


 Description   

storage_engine/trx-myisam.xa_recovery    [ fail ]
        Test ended at 2014-04-17 01:29:26
 
CURRENT_TEST: storage_engine/trx-myisam.xa_recovery
mysqltest: In included file "./include/wait_until_disconnected.inc": 
included from c:/buildbot/win-rqg-se/build-debug/mysql-test/suite/storage_engine/trx/xa_recovery.test at line 63:
At line 24: Server failed to dissapear
 
The result from queries just before the failure was:
< snip >
# If XA should be supported, check the data in Information Schema.
# ---------------------------------------------------------------------------
call mtr.add_suppression("Found 2 prepared XA transactions");
FLUSH TABLES;
DROP TABLE IF EXISTS t1;
connect  con1,localhost,root,,;
connect  con2,localhost,root,,;
connection con1;
CREATE TABLE t1 (a <INT_COLUMN>) ENGINE=<STORAGE_ENGINE> <CUSTOM_TABLE_OPTIONS>;
XA START 'xa1';
INSERT INTO t1 (a) VALUES (1),(2);
XA END 'xa1';
XA PREPARE 'xa1';
connection con2;
XA START 'xa2';
INSERT INTO t1 (a) VALUES (3);
INSERT INTO t1 (a) VALUES (4);
XA END 'xa2';
XA PREPARE 'xa2';
connection default;
 
More results from queries before failure can be found in c:\buildbot\win-rqg-se\build-debug\mysql-test\var\log\xa_recovery.log



 Comments   
Comment by Elena Stepanova [ 2018-07-19 ]

Not observed in last 3 years of recorded buildbot history.

Generated at Thu Feb 08 07:09:40 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.