Bug #75630 In PFS tests avoid validating performance_schema_max_statement_classes
Submitted: 25 Jan 2015 23:14 Modified: 1 Apr 2015 4:22
Reporter: Anitha Gopi Email Updates:
Status: Closed Impact on me:
Category:Tests: Server Severity:S3 (Non-critical)
Version:5.6 OS:Any
Assigned to: CPU Architecture:Any

[25 Jan 2015 23:14] Anitha Gopi
This is a request from Webscale


1) A number of PS tests show performance_schema_max_statement_classes
along with the other PS variables.  This value is not important, and
this number will just go up every time a new statement class is added.

The only thing testing for this number accomplishes is the creation
of pointless conflicts with all the diffs which introduce these.

So, this one variable is now excluded from the output of those tests.

2) Many internal values are included in the full output of
'show engine performance_schema status', so this has the same issue.

How to repeat:
Examine code. 

Suggested fix:

Hide the actual numerical values in the required test output.
[1 Apr 2015 4:22] Erlend Dahl
Fixed in 5.6.24.