Bug #29970 | read_only_innodb.test crashes | ||
---|---|---|---|
Submitted: | 23 Jul 2007 7:50 | Modified: | 24 Jul 2007 8:57 |
Reporter: | Ingo Strüwing | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
Version: | 5.1.21 | OS: | Linux |
Assigned to: | Georgi Kodinov | CPU Architecture: | Any |
Tags: | pbfail |
[23 Jul 2007 7:50]
Ingo Strüwing
[24 Jul 2007 8:57]
Georgi Kodinov
Ingo, I wasn't able to reproduce using exactly the same binaries on the same architecture/os. I also checked the stats for 5.1-runtime and 5.1 main : in the last 100 runs for each of the two trees this is the first occurrence of this failure. The logs (http://tinyurl.com/2h2ead) say: .... CURRENT_TEST: main.read_only_innodb 070723 5:26:53 [Note] /data0/pushbuild/pb/mysql-5.1-engines/216/mysql-5.1.21-beta-pb216/sql/mysqld: Normal shutdown 070723 5:26:53 [Note] Event Scheduler: Purging the queue. 0 events 070723 5:26:53 InnoDB: Starting shutdown... 070723 5:26:55 InnoDB: Shutdown completed; log sequence number 0 24543348 070723 5:26:55 [Note] /data0/pushbuild/pb/mysql-5.1-engines/216/mysql-5.1.21-beta-pb216/sql/mysqld: Shutdown complete CURRENT_TEST: main.rename ... So I don't think this is actually a crash. Please reopen the bug if there's more stable way to reproduce that.