innodb-system-table-view failing when run via dbqp / make test-dbqp
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drizzle |
Fix Released
|
High
|
Patrick Crews | ||
7.1 |
Fix Released
|
High
|
Patrick Crews |
Bug Description
Failing with the following diff, appears that we need to add some cleanup before the test & re-record it.
20110521-121239 innobase.
20110521-121239 --- /Users/
20110521-121239 +++ /Users/
20110521-121239 @@ -2,7 +2,7 @@
20110521-121239 TABLE_ID NAME FLAG N_COLS SPACE
20110521-121239 11 SYS_FOREIGN 0 7 0
20110521-121239 12 SYS_FOREIGN_COLS 0 7 0
20110521-121239 -13 SYS_REPLICATION_LOG 0 11 0
20110521-121239 +13 SYS_REPLICATION_LOG 0 9 0
20110521-121239 SELECT * FROM DATA_DICTIONARY
20110521-121239 INDEX_ID NAME TABLE_ID TYPE N_FIELDS PAGE_NO SPACE
20110521-121239 11 ID_IND 11 3 1 302 0
20110521-121239 @@ -25,10 +25,8 @@
20110521-121239 13 SEGID 1 6 0 4
20110521-121239 13 COMMIT_ID 2 6 0 8
20110521-121239 13 END_TIMESTAMP 3 6 0 8
20110521-121239 -13 ORIGINATING_
20110521-121239 -13 ORIGINATING_
20110521-121239 -13 MESSAGE_LEN 6 6 0 4
20110521-121239 -13 MESSAGE 7 5 4129792 0
20110521-121239 +13 MESSAGE_LEN 4 6 0 4
20110521-121239 +13 MESSAGE 5 5 4129792 0
20110521-121239 SELECT * FROM DATA_DICTIONARY
20110521-121239 INDEX_ID NAME POS
20110521-121239 11 ID 0
20110521-121239 @@ -72,7 +70,7 @@
20110521-121239 NAME FLAG N_COLS SPACE
20110521-121239 SYS_FOREIGN 0 7 0
20110521-121239 SYS_FOREIGN_COLS 0 7 0
20110521-121239 -SYS_REPLICATIO
20110521-121239 +SYS_REPLICATIO
20110521-121239 test/child 1 5 0
20110521-121239 test/parent 1 4 0
20110521-121239 SELECT name, n_fields
20110521-121239
20110521-121239 drizzletest: Result content mismatch
20110521-121239
20110521-121239
Related branches
- Drizzle Merge Team: Pending requested
-
Diff: 46 lines (+10/-1)2 files modifiedtests/lib/server_mgmt/server.py (+1/-0)
tests/lib/server_mgmt/server_management.py (+9/-1)
Changed in drizzle: | |
assignee: | nobody → Patrick Crews (patrick-crews) |
status: | New → In Progress |
importance: | Undecided → High |
milestone: | none → 2011-05-23 |
Was due to an error in dbqp after adding the backwards_ compatibility functionality.
To summarize - we weren't properly tracking that we had used an external datadir and that subsequent tests would need a reset server to ensure the expected 'pristine' state.
We were only looking at server options and so thought things were cool when the datadir was far different than expected : /
Added code to track this and properly reset the server in such cases.