percona_changed_page_bmp not runnable with release builds or Valgrind
Bug #1082437 reported by
Laurynas Biveinis
on 2012-11-23
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
Laurynas Biveinis | |
| | 5.1 |
Fix Released
|
High
|
Laurynas Biveinis | |
| | 5.5 |
Fix Released
|
High
|
Laurynas Biveinis | |
Bug Description
Testcase percona_
This division is suboptimal: the only tests that should be disabled under Valgrind are the ones using injected crashes and very fast InnoDB shutdowns. The rest of tests should be runnable under Valgrind. The name "_no_restart" is misleading as well then.
Related branches
lp:~laurynas-biveinis/percona-server/BT-16274-bug1082437-5.1
- Stewart Smith (community): Approve on 2013-01-11
-
Diff: 348 lines (+133/-116)9 files modifiedPercona-Server/mysql-test/suite/innodb_plugin/r/percona_changed_page_bmp.result (+4/-15)
Percona-Server/mysql-test/suite/innodb_plugin/r/percona_changed_page_bmp_crash.result (+32/-0)
Percona-Server/mysql-test/suite/innodb_plugin/r/percona_changed_page_bmp_no_restart.result (+0/-8)
Percona-Server/mysql-test/suite/innodb_plugin/t/percona_changed_page_bmp-master.opt (+1/-1)
Percona-Server/mysql-test/suite/innodb_plugin/t/percona_changed_page_bmp.test (+13/-60)
Percona-Server/mysql-test/suite/innodb_plugin/t/percona_changed_page_bmp_crash-master.opt (+1/-0)
Percona-Server/mysql-test/suite/innodb_plugin/t/percona_changed_page_bmp_crash.test (+82/-0)
Percona-Server/mysql-test/suite/innodb_plugin/t/percona_changed_page_bmp_no_restart-master.opt (+0/-1)
Percona-Server/mysql-test/suite/innodb_plugin/t/percona_changed_page_bmp_no_restart.test (+0/-31)
lp:~laurynas-biveinis/percona-server/BT-16274-bug1082437-5.5
- Stewart Smith (community): Approve on 2013-01-11
-
Diff: 354 lines (+139/-116)9 files modifiedPercona-Server/mysql-test/suite/innodb/r/percona_changed_page_bmp.result (+4/-15)
Percona-Server/mysql-test/suite/innodb/r/percona_changed_page_bmp_crash.result (+35/-0)
Percona-Server/mysql-test/suite/innodb/r/percona_changed_page_bmp_no_restart.result (+0/-8)
Percona-Server/mysql-test/suite/innodb/t/percona_changed_page_bmp-master.opt (+1/-1)
Percona-Server/mysql-test/suite/innodb/t/percona_changed_page_bmp.test (+13/-60)
Percona-Server/mysql-test/suite/innodb/t/percona_changed_page_bmp_crash-master.opt (+1/-0)
Percona-Server/mysql-test/suite/innodb/t/percona_changed_page_bmp_crash.test (+85/-0)
Percona-Server/mysql-test/suite/innodb/t/percona_changed_page_bmp_no_restart-master.opt (+0/-1)
Percona-Server/mysql-test/suite/innodb/t/percona_changed_page_bmp_no_restart.test (+0/-31)
Laurynas Biveinis (laurynas-biveinis)
on 2012-11-26
| summary: |
- Suboptimal test division between percona_changed_page_bmp and - *_no_restart + percona_changed_page_bmp not runnable with release builds or Valgrind |
| Shahriyar Rzayev (rzayev-sehriyar) wrote : | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/