[MDEV-12277] rocksdb.rocksdb fails with Sort Aborted error in server stderr Created: 2017-03-15 Updated: 2017-03-16 Resolved: 2017-03-16 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - RocksDB |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Major |
| Reporter: | Sergei Petrunia | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
It started to fail like this after the last merge:
maybe other tests have similar issues. The error:
The relevant rocksdb.rocksdb test:
|
| Comments |
| Comment by Sergei Petrunia [ 2017-03-15 ] | ||
|
Running the test on fb/mysql-5.6. The test passes, but var/log/mysqld.1.err has the same kind of error messages:
and looking through mysql-test/suite/rocksdb , I can't find any suppression being added for this. | ||
| Comment by Sergei Petrunia [ 2017-03-16 ] | ||
|
With Elena's help, figured that the upstream has Sort aborted stderr message globally suppressed. Should rocksdb test suite have some suite-wide suppressions? Galera has, see ../plugin/wsrep_info/mysql-test/wsrep_info/suite.pm for an example. For now, will just add a suppression to rocksdb.rocksdb. | ||
| Comment by Sergei Petrunia [ 2017-03-16 ] | ||
|
Fix pushed to bb-10.2-mariarocks. | ||
| Comment by Sergei Petrunia [ 2017-03-16 ] | ||
|
Got interested why this error message shows up now but didn't show up before. It's because the current server has log_warnings=2, while before the merge it had log_warnings=1. This is why rocksdb.rocksdb did not print Sort aborted into stderr. |