| Bug #6021 | Test 'func_compress' demands too much memory | ||
|---|---|---|---|
| Submitted: | 11 Oct 2004 12:11 | Modified: | 22 Oct 2004 17:13 |
| Reporter: | Joerg Bruehe | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Compiling | Severity: | S1 (Critical) |
| Version: | 4.1.6-gamma | OS: | Any (Any) |
| Assigned to: | Ramil Kalimullin | CPU Architecture: | Any |
[22 Oct 2004 17:13]
Michael Widenius
We do now require about 200M of ram to run test cases; This is needed to ensure that we don't have any problems with big blobs. I think this is fine for the normal test-suite. We may want to add an option to mysql-test-run to not run test that takes a lot of memory...
Description: Excerpt from build log (here: On Tru64): func_compress [ fail ] Errors are (from /local/users/mysqldev/barney/test/mysql-debug-4.1.6-gamma-dec-osf5.1-alphaev67/mysql-test/var/log/mysqltest-time) : /local/users/mysqldev/barney/test/mysql-debug-4.1.6-gamma-dec-osf5.1-alphaev67/bin/mysqltest: At line 44: query 'select compress(repeat('aaaaaaaaaa', 10000000)) is null' failed: 5: Out of memory (Needed 100000008 bytes) (the last lines may be the most important ones) Aborting: func_compress failed. To continue, re-run with '--force'. The test tries to build a string of 10 millions repetitions of 10 characters each, this gives 100 MB. Depending on build machine, user limits, ... this may fail; then no future test will be taken. The same problem has occurred during other builds / on other machines as well. Setting prio to "high", severity to "critical" because it blocks the automatic test execution. How to repeat: Run the test "func_compress" in its current shape on 'barney'. Suggested fix: Change the test so that less memory is required, - or - ensure that a failure of this test due to "Out of memory" is not considered a "test failed" and so does not terminate the test suite.