Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Won't Fix
-
5.1.67, 5.2.14, 5.3.12, 5.5, 10.0
Description
The test main.innodb_bug39438 adds a test-specific suppression via mtr.add_suppression. So far so good.
The test runner runs this test, and it passes (call mtr.check_warnings skips the expected warning).
Then, sub check_warnings_post_shutdown runs. This completely ignores any per-test warnings and finds the expected warning (that was supposed to be suppressed) in the warning log and fails:
==============================================================================
|
TEST RESULT TIME (ms)
|
------------------------------------------------------------
|
|
|
worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 13000..13009
|
main.innodb_bug39438 [ pass ] 187
|
Yoyoyoyo
|
***Warnings generated in error logs during shutdown after running tests: main.innodb_bug39
|
438
|
|
|
100129 14:58:42 InnoDB: Error: table 'test/bug39438' <-- this was supposed to be suppressed.
|
|
|
------------------------------------------------------------
|
The servers were restarted 0 times
|
Spent 0.187 of 16 seconds executing testcases
|
|
|
All 1 tests were successful.
|
|
|
Errors/warnings were found in logfiles during server shutdown after running the
|
following sequence(s) of tests:
|
main.innodb_bug39438
|
mysql-test-run: *** ERROR: There where errors/warnings in server logs after running test c
|
ases.
|
|
|
Note: mtr.add_suppression is doing its job correctly, but the _post_shutdown routine completely ignores such suppressions, only using the extract_warning_lines perl routine.