Bug #13527 mysql-test-run.pl truncates var/log/*.err several times during one testsuit run
Submitted: 27 Sep 2005 14:54 Modified: 27 Sep 2005 19:33
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0 OS:Linux (linux)
Assigned to: Guilhem Bichot CPU Architecture:Any

[27 Sep 2005 14:54] Guilhem Bichot
Running a full testsuite with
./mysql-test-run.pl --force
I have:
[DEL 16:13 /m/mysql-5.0-wl1012/mysql-test $] cat var/log/master.err
050927 17:16:59  InnoDB: Started; log sequence number 0 19573472
050927 17:17:00 [Note] /home/mysql_src/mysql-5.0-wl1012/sql/mysqld: ready for connections.
Version: '5.0.14-rc-valgrind-max-debug-log'  socket: '/home/mysql_src/mysql-5.0-wl1012/mysql-test/var/tmp/master.sock'  port: 9306  Source distribution
050927 17:17:10 [ERROR] Failed to open log (file '/home/mysql_src/mysql-5.0-wl1012/mysql-test/var/log/master-bin.000002', errno 2)
CURRENT_TEST: rpl_row_reset_slave
CURRENT_TEST: rpl_row_rewrt_db
CURRENT_TEST: rpl_row_sp007
CURRENT_TEST: rpl_row_stop_middle
CURRENT_TEST: rpl_row_until
[DEL 16:17 /m/mysql-5.0-wl1012/mysql-test $] cat var/log/slave.err
[DEL 16:17 /m/mysql-5.0-wl1012/mysql-test $] cat var/log/slave.err
050927 17:17:58 [Note] /home/mysql_src/mysql-5.0-wl1012/sql/mysqld: ready for connections.
Version: '5.0.14-rc-valgrind-max-debug-log'  socket: '/home/mysql_src/mysql-5.0-wl1012/mysql-test/var/tmp/slave.sock'  port: 9308  Source distribution
[DEL 16:17 /m/mysql-5.0-wl1012/mysql-test $]

See: the var/log/master.err starts at the last master restart (while with the shell version of mysql-test-run it starts at the first master start of the testsuite) and so misses all that happened before rpl_row_reset_slave. The var/log/slave.err is even empty when I first look into it (it has just been recreated apparently).

How to repeat:
run the full testsuite and see how var/log/*.err evolve: they shrink sometimes instead of growing all the time.

Suggested fix:
pass { append_log_file => 1 }.
[27 Sep 2005 19:33] Guilhem Bichot
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

nothing to document (the problem was just a detail in our testsuite script mysql-test-run.pl, not causing trouble to users, just causing difficulties to us devs for debugging our tests).