Bug #27799 mysqldump test failure on irix
Submitted: 13 Apr 2007 3:02 Modified: 12 May 2009 10:20
Reporter: Peter O'Gorman Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Tests Severity:S3 (Non-critical)
Version:5.0.38 OS:Other (IRIX-6.5)
Assigned to: CPU Architecture:Any
Tags: IRIX, Tests

[13 Apr 2007 3:02] Peter O'Gorman
Description:
Bug 25343 lists some tests that fail on IRIX, those fail for us too. We also get an odd failure for the mysqldump test. The failure summary says:
mysql-test-run in default mode: *** Failing the test(s): mysqlbinlog2 mysqldump ps_2myisam ps_3innodb ps_4heap ps_5merge ps_6bdb rpl000002 sp timezone timezone4 type_float, this bug is only about the mysqldump failure.

The reason it is odd is that the output is very similar, the only difference is the location in the log of the error message.
diff -u /opt/build/mysql-5.0.38/mysql-test/r/mysqldump.reject /opt/build/mysql-5.0.38/mysql-test/r/mysqldump.result
--- /opt/build/mysql-5.0.38/mysql-test/r/mysqldump.reject     Fri Apr 13 01:41:10 2007
+++ /opt/build/mysql-5.0.38/mysql-test/r/mysqldump.result       Tue Mar 20 19:25:52 2007
@@ -1757,6 +1757,8 @@
 # Bug #21288: mysqldump segmentation fault when using --where
 #
 create table t1 (a int);
+mysqldump: Couldn't execute 'SELECT /*!40001 SQL_NO_CACHE */ * FROM `t1` WHERE xx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx': You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' at line 1 (1064)
+mysqldump: Got error: 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' at line 1 when retrieving data from server

 /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
 /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
@@ -1772,8 +1774,6 @@
 CREATE TABLE `t1` (
   `a` int(11) default NULL
 ) ENGINE=MyISAM DEFAULT CHARSET=latin1;
-mysqldump: Couldn't execute 'SELECT /*!40001 SQL_NO_CACHE */ * FROM `t1` WHERE xx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx': You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' at line 1 (1064)
-mysqldump: Got error: 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' at line 1 when retrieving data from server

 /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;

As you can see the errors are the same but the context is different. See a side-by-side screenshot of the two at <http://pogma.com/misc/Screenshot.png>

The results are so similar that I believe the test is buggy in reporting this as a failure.

How to repeat:
Run the test suite on irix.

Suggested fix:
Disable that part of the test, or make it somehow 'fuzzy' so that it can detect the issue.
[13 Apr 2007 7:36] Valeriy Kravchuk
Thank you for a problem report. Please, send the results of

env

command from your testing environment.
[13 Apr 2007 14:08] Peter O'Gorman
This is the env from the test.

STY=756023.build
TERM=screen
TERMCAP=SC|screen|VT 100/ANSI X3.64 virtual terminal:\
        :DO=\E[%dB:LE=\E[%dD:RI=\E[%dC:UP=\E[%dA:bs:bt=\E[Z:\
        :cd=\E[J:ce=\E[K:cl=\E[H\E[J:cm=\E[%i%d;%dH:ct=\E[3g:\
        :do=^J:nd=\E[C:pt:rc=\E8:rs=\Ec:sc=\E7:st=\EH:up=\EM:\
        :le=^H:bl=^G:cr=^M:it#8:ho=\E[H:nw=\EE:ta=^I:is=\E)0:\
        :li#22:co#80:am:xn:xv:LP:sr=\EM:al=\E[L:AL=\E[%dL:\
        :cs=\E[%i%d;%dr:dl=\E[M:DL=\E[%dM:dc=\E[P:DC=\E[%dP:\
        :im=\E[4h:ei=\E[4l:mi:IC=\E[%d@:ks=\E[?1h\E=:\
        :ke=\E[?1l\E>:vi=\E[?25l:ve=\E[34h\E[?25h:vs=\E[34l:\
        :ti=\E[?1049h:te=\E[?1049l:so=\E[3m:se=\E[23m:mb=\E[5m:\
        :md=\E[1m:mr=\E[7m:me=\E[m:ms:\
        :Co#8:pa#64:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:AX:G0:\
        :as=\E(0:ae=\E(B:\
        :ac=\140\140aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~..--++,,hhII00:\
        :Z0=\E[?3h:Z1=\E[?3l:k0=\E[10~:k1=\EOP:k2=\EOQ:k3=\EOR:\
        :k4=\EOS:k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:\
        :k9=\E[20~:k;=\E[21~:F1=\E[23~:F2=\E[24~:kb=^H:K1=\EOq:\
        :K2=\EOr:K3=\EOs:K4=\EOp:K5=\EOn:kh=\E[1~:@1=\E[1~:\
        :kH=\E[4~:@7=\E[4~:kN=\E[6~:kP=\E[5~:kI=\E[2~:kD=\E[3~:\
        :ku=\EOA:kd=\EOB:kr=\EOC:kl=\EOD:km:
WINDOW=1
SHELL=/opt/fsw/bin/zsh
USER=pogma
LOGNAME=pogma
HOME=/home/pogmaPATH=/opt/TWWfsw/perl586/bin:/home/pogma/bin:/opt/fsw/bin:/opt/tww/bin:/bin:/usr/bin:/sbin:/usr/sbin:/etc:/usr/etc:/usr/bin/X11:/usr/bsd
MAIL=/usr/mail//pogma
SSH_CLIENT=192.168.1.1 63734 22
SSH_CONNECTION=192.168.1.1 63734 192.168.1.33 22
SSH_TTY=/dev/ttyq9
SHLVL=2
PWD=/opt/build/mysql-5.0.38/mysql-test
OLDPWD=/home/pogma
HISTSIZE=1000
EDITOR=vim
_=/bin/en
[19 Apr 2007 16:31] Sveta Smirnova
Thank you for the report.

Test failure is verified with anoter message:

mysqldump                      [ fail ]

Errors are (from /***/sveta/src/mysql-5.0/mysql-test/var/log/mysqltest-time) :
mysqldump: Couldn't find table: "non_existing"
mysqldump: Couldn't execute 'show table status like 'v2'': Lost connection to MySQL server during query (2013)
mysqltest: At line 755: command "$MYSQL_DUMP  --skip-comments db1" failed
[8 Jun 2007 21:09] Joerg Behrens
Looks like a duplicate #25285. A workaround is available.

regards
Joerg
[12 May 2009 10:20] Philip Stoev
According to

http://www.mysql.com/support/supportedplatforms/enterprise.html

and to the build team, we do not support IRIX anymore.