Bug #8783 | Test 'kill' fails: NULL vs. 0 | ||
---|---|---|---|
Submitted: | 24 Feb 2005 17:19 | Modified: | 24 Feb 2005 18:15 |
Reporter: | Joerg Bruehe | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0.3-pre | OS: | several Unix |
Assigned to: | Guilhem Bichot | CPU Architecture: | Any |
[24 Feb 2005 17:19]
Joerg Bruehe
[24 Feb 2005 18:06]
Guilhem Bichot
was able to repeat on powermacg5. Not caused by me but I fix it now.
[24 Feb 2005 18:15]
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 http://www.mysql.com/doc/en/Installing_source_tree.html Additional info: ChangeSet@1.1848, 2005-02-24 19:13:55+01:00, guilhem@mysql.com Fix for BUG#8783 kill.test must always sleep 2 seconds, even if mysql-test-run runs with --sleep=10; otherwise GET_LOCK() times out before being killed so we get 0 instead of NULL. Verified that it works on our powermacg5 where the test was failing.