Bug #22074 mysql-test-run.pl abort test run if it fails to start instance manager
Submitted: 7 Sep 2006 9:27 Modified: 3 Oct 2006 20:27
Reporter: Magnus Blåudd Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Tests Severity:S3 (Non-critical)
Version:5.0.25 OS:
Assigned to: Alexander Nozdrin CPU Architecture:Any

[7 Sep 2006 9:27] Magnus Blåudd
Description:
If mysql-test-run.pl fails to start instance manager the holw test suite run will be aborted with error "failed to start im in 30 seconds".

How to repeat:
I belive we saw the above problem when running on a mcahine with port conflicts for im. But is should be possible to repeat by mocifying the script a little to make im start fail.

Suggested fix:
The script should continue but mark the test as failed, printing a warning about the failure to start im in 30 secs.
[8 Sep 2006 12:41] 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/11616

ChangeSet@1.2262, 2006-09-08 16:41:35+04:00, anozdrin@alik. +1 -0
  Fix for BUG#22074: mysql-test-run.pl abort test run if it fails
  to start instance manager.
  
  The problem was that if IM failed to start, test suite aborts.
  
  The fix is to mark current test as failed, and continue running
  test suite.
  
  The fix affects only test suite.
[8 Sep 2006 13:12] Magnus Blåudd
Very good. Thank you!
[3 Oct 2006 19:40] Dmitry Lenev
Fixed in 5.0.27 and 5.1.12.
[3 Oct 2006 20:27] Paul Dubois
Test suite change. No changelog entry needed.