| Bug #42979 | ndb.ndb_read_multi_range crashes on sol10-sparc64 and powermacg5 | ||
|---|---|---|---|
| Submitted: | 18 Feb 2009 17:02 | Modified: | 29 Sep 2009 10:53 |
| Reporter: | Alexander Nozdrin | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
| Version: | 6.0-TRUNK | OS: | Any |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | crash, disabled, pb2, pushbuild, test failure | ||
[18 Feb 2009 17:04]
Alexander Nozdrin
Log and stack trace.
Attachment: qqq.txt (text/plain), 37.08 KiB.
[26 Feb 2009 9:16]
Alexander Nozdrin
Now we have a failure on powermacg5 also: http://tinyurl.com/dxm25z
[2 Mar 2009 13:50]
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/67992 3047 Alexander Nozdrin 2009-03-02 Disable ndb_read_multi_range.test on Mac OS due to Bug#42979 modified: mysql-test/suite/ndb/t/ndb_read_multi_range.test
[2 Mar 2009 13:53]
Alexander Nozdrin
The test case is disabled on Mac OS.
[2 Mar 2009 14:13]
Bugs System
Pushed into 6.0.11-alpha (revid:alik@sun.com-20090302140208-lfdejjbcyezlhhjt) (version source revid:alik@sun.com-20090302135029-yppjfn8kjq92jg7l) (merge vers: 6.0.11-alpha) (pib:6)
[20 Aug 2009 10:22]
Andrei Elkin
Happened recently: http://pb2.norway.sun.com/web.py?template=push_details&push=496083
Description: ndb.ndb_read_multi_range crashes on Solaris10/sparc64. Symptoms: ------------------------------------------------------- ndb.ndb_read_multi_range [ fail ] Test ended at 2009-02-17 15:00:02 CURRENT_TEST: ndb.ndb_read_multi_range mysqltest: At line 295: query 'select t21.* from t21,t22 where t21.a = t22.a and t22.a in (select t12.a from t11, t12 where t11.a in(255,256) and t11.a = t12.a and t11.c is null) and t22.c is null order by t21.a' failed: 2013: Lost connection to MySQL server during query The result from queries just before the failure was: < snip > 4101 67 NULL 9199 67 NULL 223456 67 NULL 245651 67 2005-12-08 15:58:27 245652 67 2005-12-08 15:58:27 245653 67 2005-12-08 15:59:07 245654 67 2005-12-08 15:59:08 245655 67 2005-12-08 15:59:08 398340 67 2006-02-20 04:38:53 398341 67 2006-02-20 04:48:44 398545 67 2006-02-20 04:53:13 406631 67 2006-02-23 10:49:42 406988 67 2006-02-23 17:07:22 406989 67 2006-02-23 17:08:46 406990 67 2006-02-23 18:01:45 406991 67 2006-02-24 16:42:32 406992 67 2006-02-24 16:47:18 406993 67 2006-02-27 11:20:57 406994 67 2006-02-27 11:26:46 406995 67 2006-02-28 11:55:00 ------------------------------------------------------- Full log is attached. Reported after a failure on 2009-02-17 in 6.0-main. How to repeat: XRef2: http://tinyurl.com/bp8bab