Test innodb.percona_changed_page_bmp_crash is unstable

Bug #1658021 reported by Laurynas Biveinis on 2017-01-20
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.5
Invalid
Undecided
Unassigned
5.6
Fix Released
Low
Laurynas Biveinis
5.7
Fix Released
Low
Laurynas Biveinis

Bug Description

On 5.6 trunk:

innodb.percona_changed_page_bmp_crash w3 [ fail ]
        Test ended at 2016-12-23 15:01:41

CURRENT_TEST: innodb.percona_changed_page_bmp_crash
safe_process[4306]: Child process: 4307, killed by signal: 9
...
2016-12-23 18:01:39 5272 [Note] /mnt/workspace/percona-server-5.6-trunk/BUILD_TYPE/debug/Host/centos6-64/build/sql/mysqld-debug: ready for connections.
Version: '5.6.34-79.1-debug-log' socket: '/tmp/ca0TtRabB0/3/mysqld.1.sock' port: 13021 MySQL Community Server (GPL)
SIGKILL myself
safe_process[5271]: Child process: 5272, killed by signal: 9

tags: added: bitmap ci xtradb

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2223

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers