Bug #15199 broken web link --> http://www.mysql.com/doc/en/MySQL_test_suite.html
Submitted: 23 Nov 2005 20:01 Modified: 8 Mar 2006 1:26
Reporter: [ name withheld ] Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.16 OS:IBM AIX (AIX 5.2)
Assigned to: Kent Boortz CPU Architecture:Any

[23 Nov 2005 20:01] [ name withheld ]
Description:
When running the mysql-test-run in /usr/local/mysql/mysql-test directory and got 2 failed tests out of 351 tests.  The comment and the link was provided at the bottom..

--snip--
windows                        [ skipped ]
xa                             [ pass ]   
-------------------------------------------------------

Ending Tests
Shutting-down MySQL daemon

Master shutdown finished
Slave shutdown finished
Failed 2/351 tests, 99.43% were successful.

The log files in /usr/local/mysql/mysql-test/var/log may give you some hint
of what went wrong.
If you want to report this error, please read first the documentation at
http://www.mysql.com/doc/en/MySQL_test_suite.html

mysql-test-run in default mode: *** Failing the test(s): func_compress rpl_rotate_logs
--snip--

There, the link to the www.mysql.com/doc/en/MySQL_test_suite.html is a broken link since the web page is not found on that web site, so I can not report the error.

How to repeat:
Just run the mysql-test-run script and wait a while for it to finish, then you'll have your chance with the comment at the bottom.

Suggested fix:
Fix hte broken link.
[23 Nov 2005 20:40] [ name withheld ]
Updating the Synopsis (Title).
[24 Nov 2005 0:14] Hartmut Holzgraefe
The URL works fine for me and redirects to the appropriate page in the MySQL 5.0 manual
(maybe a temporary redirection failure)
but as the manuals are now version specific i'll keep this report open 
as a request for the URL to be changed to point to the page in the
appropriate manual version right away without redirection
[28 Nov 2005 13:59] [ name withheld ]
It worked now so you're correct about the temporary redirection failure.  I would have no way of knowing of that at first but you're right we wouldn't want to cause the some users an inconvience.  So, do whatever you think is best for this bug report and I'll go along with it.