Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0(EOL)
-
None
-
5.5.55, 10.0.30
Description
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);
|
Attachments
Issue Links
- is blocked by
-
MDEV-12106 Valgrind tests fail all over in buildbot on 10.0 with blocks are still reachable
-
- Closed
-
- relates to
-
MDEV-7069 Fix buildbot failures in main server trees
-
- Closed
-
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.