Bug #44903 MTR should try to free disk space if available disk space is below some limit

Submitted:	15 May 2009 13:30	Modified:	3 Jun 2009 19:28
Reporter:	Matthias Leich	Email Updates:
Status:	Verified	Impact on me:	None
Category:	Tools: MTR / mysql-test-run	Severity:	S3 (Non-critical)
Version:	5.1,5.4,6.0	OS:	Any
Assigned to:	Bjørn Munch	CPU Architecture:	Any

Description:
MTR tries to optimise the execution of testsuites by
running of sequencies of tests without server shutdown,
whatever, server restart between.

This has the unfortunate effect that some more general
and storage engine related logs can grow to a dramatic
size. I fear also that the space for InnoDB table
content grows.
These effects can or at least could be observed when
running the Partitioning testsuite.

It would be nice if MTR would try to free disk space
(vardir,tmpdir related) if the available space
(vardir,tmpdir related) falls below some configurable
limit.

How to repeat:
See above

Suggested fix:
In case the current testcase A passed and the next
testcase B does not require a server restart
please do the following:
1. Check if the free disk space (available for tmpdir,
   vardir) is below some configurable limit
2. Above the limit: do nothing
   Below limit: Behave as if testcase A had failed
         = shutdown server, recreate databases etc,
           server restart
3. Run testcase B

Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.