[MDEV-11767] innodb.innodb_bug53290, innodb_fts.innodb_fts_misc, percona.percona_xtradb_bug317074 fail in buildbot under valgrind with timeout Created: 2017-01-11  Updated: 2017-02-25  Resolved: 2017-02-25

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

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Elena Stepanova
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by MDEV-12106 Valgrind tests fail all over in build... Closed
Relates
relates to MDEV-7069 Fix buildbot failures in main server ... Stalled
Sprint: 5.5.55, 10.0.30

 Description   

http://buildbot.askmonty.org/buildbot/builders/xenial-amd64-valgrind/builds/287/steps/test/logs/stdio

innodb.innodb_bug53290 'xtradb'          w10 [ fail ]  timeout after 9000 seconds
        Test ended at 2017-01-10 14:36:48
 
Test case timeout after 9000 seconds
 
== /dev/shm/var/10/log/innodb_bug53290.log == 
create table bug53290 (x bigint) engine=innodb;
insert into bug53290 () values (),(),(),(),(),(),(),(),(),(),(),();
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
alter table bug53290 add unique index `idx` (x);



 Comments   
Comment by Elena Stepanova [ 2017-02-21 ]

In recent history the tests only failed with timeouts on xenial-valgrind builder and some on p8. Power timeout failures will hopefully be resolved by switching to --mem, and we are back from xenial-based valgrind to work-valgrind. It's impossible to say now how long the tests take there, because on 10.0 the build fails due to MDEV-12106. After it's fixed, we can see whether we are getting any timeouts or if test timing is close to getting them.

Comment by Elena Stepanova [ 2017-02-24 ]

work-amd64-valgrind

innodb.innodb_bug53290 'innodb_plugin'   w1 [ pass ]  866026
innodb.innodb_bug53290 'xtradb'          w3 [ pass ]  1440900
innodb_fts.innodb_fts_misc 'innodb_plugin' w1 [ pass ]  506763
innodb_fts.innodb_fts_misc 'xtradb'      w3 [ pass ]  2708953
percona.percona_xtradb_bug317074 'xtradb' w2 [ pass ]  2707923

p8-trusty-bintar-debug

innodb_fts.innodb_fts_misc 'innodb_plugin' w2 [ pass ]  30961
innodb_fts.innodb_fts_misc 'xtradb'      w3 [ pass ]  21227
innodb.innodb_bug53290 'innodb_plugin'   w2 [ pass ]  20653
innodb.innodb_bug53290 'xtradb'          w3 [ pass ]  38438
percona.percona_xtradb_bug317074 'xtradb' w4 [ pass ]  123132

Comment by Elena Stepanova [ 2017-02-25 ]

Given the timing on work-valgrind and p8 with --mem, hopefully these particular tests won't time out, although they are still awfully slow with valgrind.

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