Bug #14822 | Test "mysqldump" fails, "result" protocol seems wrong. | ||
---|---|---|---|
Submitted: | 10 Nov 2005 11:00 | Modified: | 2 Dec 2005 4:07 |
Reporter: | Joerg Bruehe | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.0 and up | OS: | Any (All) |
Assigned to: | Ramil Kalimullin | CPU Architecture: | Any |
[10 Nov 2005 11:00]
Joerg Bruehe
[10 Nov 2005 15:00]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/32145
[10 Nov 2005 15:25]
Ramil Kalimullin
fixed in 5.0.16
[11 Nov 2005 17:24]
Lenz Grimmer
Part of the error still occurs, but only when run out of a binary distribution installation directory and when using the Perl version of mysql-test-run (the shell version passes): TEST RESULT ------------------------------------------------------- mysqldump [ fail ] Errors are (from /home/mysqldev/lenz/mysql-pro-gpl-5.0.16-linux-i686-csc7204/mysql-test/var/log/mysqltest-time) : sh: line 1: -uroot: command not found mysqltest: At line 708: command "$MYSQL_IMPORT test $MYSQL_TEST_DIR/var/tmp/t1.txt" failed (the last lines may be the most important ones)
[2 Dec 2005 4:07]
Paul DuBois
No changelog entry needed.