[MDEV-10617] federated.federatedx, federated.federated_innodb, federated.federated_transactions fail sporadically in buildbot Created: 2016-08-20  Updated: 2023-11-29  Resolved: 2023-11-29

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

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

Attachments: HTML File consoleText    
Issue Links:
Relates
relates to MDEV-7069 Fix buildbot failures in main server ... Stalled

 Description   

The test produces different kinds of failures in buildbot.

http://buildbot.askmonty.org/buildbot/builders/p8-xenial-bintar/builds/90

federated.federatedx 'X'                 w4 [ fail ]
        Test ended at 2016-08-05 04:04:51
 
CURRENT_TEST: federated.federatedx
--- /var/lib/buildbot/maria-slave/p8-xenial-bintar/build/mysql-test/suite/federated/federatedx.result	2016-08-05 03:18:19.566373832 -0400
+++ /var/lib/buildbot/maria-slave/p8-xenial-bintar/build/mysql-test/suite/federated/federatedx.reject	2016-08-05 04:04:51.357163484 -0400
@@ -2213,7 +2213,7 @@
 CONNECTION='mysql://root@127.0.0.1:SLAVE_PORT/test/t1';
 CHECKSUM TABLE t1;
 Table	Checksum
-test.t1	2465757603
+test.t1	229274939
 connection slave;
 DROP TABLE t1;
 connection master;
 
mysqltest: Result length mismatch

http://askmonty.org/buildbot/builders/work-amd64-valgrind/builds/8996

federated.federatedx 'X'                 w3 [ fail ]
        Test ended at 2016-06-29 07:51:30
 
CURRENT_TEST: federated.federated_partition
CURRENT_TEST: federated.federated_partition
CURRENT_TEST: federated.assisted_discovery
CURRENT_TEST: federated.federatedx
 
 
Failed to start mysqld.1

http://buildbot.askmonty.org/buildbot/builders/p8-trusty-bintar/builds/92

federated.federated_transactions 'X,xtradb' w4 [ fail ]
        Test ended at 2016-08-14 09:36:20
 
CURRENT_TEST: federated.federated_transactions
mysqltest: At line 37: query 'DELETE FROM federated.t1' failed: 1159: Got timeout reading communication packets
 
The result from queries just before the failure was:
< snip >
    )
ENGINE="FEDERATED" DEFAULT CHARSET=latin1
CONNECTION='mysql://root@127.0.0.1:SLAVE_PORT/federated/t1';
set autocommit=0;
INSERT INTO federated.t1 (id, name) VALUES (1, 'foo');
INSERT INTO federated.t1 (id, name) VALUES (2, 'fee');
COMMIT;
INSERT INTO federated.t1 (id, name) VALUES (3, 'fie');
INSERT INTO federated.t1 (id, name) VALUES (4, 'fum');
ROLLBACK;
set autocommit=1;
INSERT INTO federated.t1 (id, name) VALUES (5, 'foe');
INSERT INTO federated.t1 (id, name) VALUES (6, 'fig');
SELECT * FROM federated.t1;
id	name
1	foo
2	fee
5	foe
6	fig
DELETE FROM federated.t1;



 Comments   
Comment by Elena Stepanova [ 2016-09-01 ]

danblack, this attachment doesn't belong here, it's more like MDEV-9152 / MDEV-10417 / MDEV-8691 (but probably the first one, since it's also ppc64).

Comment by Daniel Black [ 2016-09-01 ]

MDEV-9152 look like a big endian problem that has gone away. This might still be the last build failure http://buildbot.askmonty.org/buildbot/builders/p8-trusty-bintar/builds/92 though its a bit hard to say.

First checksum error here was fixed with https://github.com/MariaDB/server/commit/a2c826b6aa38d68e79a80499b0ecdc57ae98f8e0 (the wrong crc32 variant was in the build tree for a little bit).

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