Bug #37770 | rpl_ps/row fails sporadically | ||
---|---|---|---|
Submitted: | 1 Jul 2008 15:12 | Modified: | 6 Aug 2008 15:12 |
Reporter: | Alexander Nozdrin | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | Tests: Replication | Severity: | S3 (Non-critical) |
Version: | 6.0-BK | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | pushbuild, reason unknown, sporadic, test failure |
[1 Jul 2008 15:12]
Alexander Nozdrin
[6 Aug 2008 15:12]
Sven Sandberg
The message "failed to start mysqld" just indicates that a server has crashed. It is usually not related to a specific test. The xref page above likely does not identify a unique error: many errors can have these symptoms. We have several bugs reported where the symptom is "failed to start mysqld". So I'm closing this as a duplicate (of, e.g., Bug#37714, BUG#38555, or Bug#38286, BUG#37841). If you think that a particular failure is different from any of these, please provide: - an url to the push that fails (identifying not only the tree, but also the push number) - the host where it fails (e.g., sapsrv1) - the suite where it fails (e.g., ps_row)