Bug #24389 mysqltest: Could not open connection 'default': 2013 Lost connection to MySQL
Submitted: 17 Nov 2006 11:39 Modified: 10 Dec 2006 1:42
Reporter: Lars Thalmann Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0 source OS:
Assigned to: Kristofer Pettersson CPU Architecture:Any

[17 Nov 2006 11:39] Lars Thalmann 
Description:
Running the test suite in Pushbuild with Valgrind enabled,
case the client to loose contact with the MySQL server.

How to repeat:
Pushbuild

Suggested fix:
Perhaps it is a simple timeout in the test suite that needs to 
be modified?  Perhaps it is something much more complex.
[1 Dec 2006 15:27] 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/commits/16316

ChangeSet@1.2576, 2006-12-01 16:23:14+01:00, msvensson@neptunus.(none) +2 -0
  Bug#24389 mysqltest: Could not open connection 'default': 2013 Lost connection to MySQL
   - When vio_pool_read, return error code inidcating connection to server could not
     be established.
   - Add CR_CONN_HOST_ERROR to list of errorcode that trigger another connection
     attempt in mysqltest
[4 Dec 2006 14:51] 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/commits/16389

ChangeSet@1.2576, 2006-12-04 15:48:34+01:00, msvensson@neptunus.(none) +1 -0
  Bug#24389 mysqltest: Could not open connection 'default': 2013 Lost connection to MySQL
   - Add CR_CONN_HOST_ERROR to list of errorcode that trigger another connection
     attempt in mysqltest
[10 Dec 2006 1:42] Paul DuBois 
No changelog entry needed.