| Bug #17576 | Too many failed cluster restarts timeout mysql-test-run.pl | ||
|---|---|---|---|
| Submitted: | 20 Feb 2006 11:45 | Modified: | 3 Aug 2006 15:36 |
| Reporter: | Magnus Blåudd | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | OS: | ||
| Assigned to: | Magnus Blåudd | CPU Architecture: | Any |
Fixed in 5.1
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.012 sec. using MySQL 8.0.36-u4-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
© 2024, Oracle Corporation and/or its affiliates
Description: - If all ndb test cases fail, but manage to restart the cluster, the whole test suite times out, as this takes too long time. This problem is not specific to ndb. One solution is that after N restarts in total, the suite gives up and teturn error. Or do a specific solution for ndb, that after N failing ndb restarts, just mark the remaining ndb test cases as failed. How to repeat: - If all ndb test cases fail, but manage to restart the cluster, the whole test suite times out, as this takes too long time. This problem is not specific to ndb. One solution is that after N restarts in total, the suite gives up and teturn error. Or do a specific solution for ndb, that after N failing ndb restarts, just mark the remaining ndb test cases as failed.