percona_changed_page_bmp not runnable with release builds or Valgrind

Bug #1082437 reported by Laurynas Biveinis
6
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_changed_page_bmp contains the bulk of bitmap writer tests, but it's disabled under Valgrind. Testcase percona_changed_page_bmp_no_restart is not disabled under Valgrind, but contains only rudimentary tests.

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

summary: - Suboptimal test division between percona_changed_page_bmp and
- *_no_restart
+ percona_changed_page_bmp not runnable with release builds or Valgrind
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.