[MCOL-2150] Failed tests in the ?01 suite Created: 2019-02-08 Updated: 2023-03-06 Resolved: 2023-03-06 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | ExeMgr |
| Affects Version/s: | 1.2.2 |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Major |
| Reporter: | Patrick LeBlanc (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Ubuntu 18 dev environment |
||
| Attachments: |
|
|||||||||||||||||||||||||||||||||||
| Sub-Tasks: |
|
| Description |
|
I found a several query failures trying to get baseline results to test against our work on S3 so far. Roman & I looked into a couple, and at least what we investigated are legitimate bugs, not some environmental difference. One thing needs to happen right away: turn on result comparisons in our regression test suite. It's really important to know when we've broken something. A little more looking makes me think some references are bad, and some are missing, so it's not necessarily all broken. But we need to get back to all of the tests we run actually pass. I tested the code at the following commits in the develop-1.2 branches: I'll attach the results I got running a baseline test. Failures are listed at the bottom of each file. |
| Comments |
| Comment by Patrick LeBlanc (Inactive) [ 2019-02-08 ] |
|
A couple notes on the log files above 1) In working_tpch1, rename.negative.sql crashed mysqld, which I took out of the test so I could keep moving forward. Roman's already working on that one. 2) The results in working_tpch1_comparelogonly are partial. something in the regr test set is crashing exemgr. I haven't followed up on that yet. |
| Comment by Todd Stoffel (Inactive) [ 2023-03-06 ] |
|
This ticket was created prior to convergence with the server and may be obsolete. If you find this issue still exists in a modern version, please open a new ticket. |