Description:
When "mysql-test-run.pl" ("MTR") extracts messages from the server log,
it starts much too early and includes lines from tests that passed since long.
These irrelevant lines both make it hard to find the relevant info and blow up the file, increasing storage demands and processing time.
As a sample case, take bug#48204:
The test failure occurs 117 times,
and extracting this failure from the log yields files of 425 - 435 kB (21 times) or more than 1.3 MB (96 times).
The "small" files have about 3,900 lines each, and the extract for the current test starts at line 3,877;
the large files have about 13,600 lines each, and again the current test is in the last (about) 30 lines only.
Because of human work time, disk space, and CPU time, we cannot afford this inefficieent extract.
How to repeat:
Look at bug#48204.
Suggested fix:
Limit the extract to the correct "CURRENT_TEST".
If it is considered essential to have the lines leading to that,
either take a fixed number of lines before that
or note the name of the preceding test, start from that.
I know the description reminds of bug#46973,
but that is documented to be pushed into this release, so it is either a different problem or that fix isn't effective.
Description: When "mysql-test-run.pl" ("MTR") extracts messages from the server log, it starts much too early and includes lines from tests that passed since long. These irrelevant lines both make it hard to find the relevant info and blow up the file, increasing storage demands and processing time. As a sample case, take bug#48204: The test failure occurs 117 times, and extracting this failure from the log yields files of 425 - 435 kB (21 times) or more than 1.3 MB (96 times). The "small" files have about 3,900 lines each, and the extract for the current test starts at line 3,877; the large files have about 13,600 lines each, and again the current test is in the last (about) 30 lines only. Because of human work time, disk space, and CPU time, we cannot afford this inefficieent extract. How to repeat: Look at bug#48204. Suggested fix: Limit the extract to the correct "CURRENT_TEST". If it is considered essential to have the lines leading to that, either take a fixed number of lines before that or note the name of the preceding test, start from that. I know the description reminds of bug#46973, but that is documented to be pushed into this release, so it is either a different problem or that fix isn't effective.