Bug #17574 Detect cluster start failure and "fail" ndb_* tests
Submitted: 20 Feb 2006 11:43 Modified: 9 Mar 2006 12:04
Reporter: Magnus Blåudd Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version: OS:
Assigned to: Magnus Blåudd CPU Architecture:Any

[20 Feb 2006 11:43] Magnus Blåudd 
Description:
  - When the suite starts, it can't start ndb. What about just record
    this and continue with ndb disabled. But not to fool yourself all
    went well, let each ndb test case report "failed" instead of
    "skipped". I know not striclty correct, but my problem is that if
    ndb doesn't start, I get nothing. All ndb failing gets my
    attention, and still information about possible other test
    failures.

How to repeat:
  - When the suite starts, it can't start ndb. What about just record
    this and continue with ndb disabled. But not to fool yourself all
    went well, let each ndb test case report "failed" instead of
    "skipped". I know not striclty correct, but my problem is that if
    ndb doesn't start, I get nothing. All ndb failing gets my
    attention, and still information about possible other test
    failures.
[7 Mar 2006 18:44] 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/3550
[7 Mar 2006 19:35] 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/3552
[8 Mar 2006 15:57] 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/3589
[9 Mar 2006 12:04] Magnus Blåudd 
Pushed to 5.0 and 5.1