| Bug #59775 | Some tests failing on windows in daily-trunk due to database corruption | ||
|---|---|---|---|
| Submitted: | 27 Jan 2011 11:42 | Modified: | 2 Feb 2011 6:13 |
| Reporter: | Anitha Gopi | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
| Version: | mysql-trunk | OS: | Microsoft Windows |
| Assigned to: | Kevin Lewis | CPU Architecture: | Any |
| Tags: | pb2 | ||
[2 Feb 2011 4:59]
Anitha Gopi
There were some problems with the windows setup in PB2 on that day. This might have been due to that. These failures are not seen after the windows issue was resolved
Description: main.comment_column and main.lowercase_table4 fail on windows in daily-trunk main.comment_column w3 [ fail ] Test ended at 2011-01-26 05:14:20 CURRENT_TEST: main.comment_column 110126 5:14:20 InnoDB: The InnoDB memory heap is disabled 110126 5:14:20 InnoDB: Mutexes and rw_locks use Windows interlocked functions 110126 5:14:20 InnoDB: Compressed tables use zlib 1.2.3 110126 5:14:20 InnoDB: Initializing buffer pool, size = 8.0M 110126 5:14:20 InnoDB: Completed initialization of buffer pool 110126 5:14:20 InnoDB: highest supported file format is Barracuda. InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 299. InnoDB: You may have to recover from a backup. How to repeat: http://pb2.norway.sun.com/?template=mysql_show_test_failure&test_failure_id=3480990 http://pb2.norway.sun.com/?template=mysql_show_test_failure&test_failure_id=&test_output_i...