Move that perror test to ndb_basic so it's only run when there is support for --ndb
mysql-test/r/ndb_basic.result:
Move test of "perror --ndb" to this file
mysql-test/r/perror.result:
Move test of "perror --ndb" to ndb_basic
mysql-test/t/ndb_basic.test:
Move test of "perror --ndb" to this file
mysql-test/t/perror.test:
Move test of "perror --ndb" to ndb_basic
mysql-test/r/perror.result:
Add error result for 1186
Remove the result for the others
mysql-test/t/perror.test:
As it's only just interesting to see that perror doesn't crash(and as result varies across platforms), send result to /dev/null
- Since error 1186 is not found among NDB error codes, the message retuned should indicate that.
extra/perror.c:
Move the !found out one level
mysql-test/t/perror.test:
Add test case for bug#16561
ndb/src/kernel/error/ndbd_exit_codes.c:
Check not only for zero size string but also classification "unknown error" when looking for an error mesage for an error code
- Add test case(execute perror)
- Check if strerror has returned NULL and set msg to "Unknown Error" in that case
- Thanks to Steven Xie for pointing out how to fix.
extra/perror.c:
strerror might return NULL on Solaris 2.8
mysql-test/mysql-test-run.pl:
Add possibility to execute perror from test case
mysql-test/r/have_perror.require:
New BitKeeper file ``mysql-test/r/have_perror.require''
mysql-test/r/perror.result:
New BitKeeper file ``mysql-test/r/perror.result''
mysql-test/t/perror.test:
New BitKeeper file ``mysql-test/t/perror.test''
