[SERVER-70080] [CQF] Consider saving memo as separate build artifact Created: 28/Sep/22 Updated: 11/Apr/23 Resolved: 11/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Percy | Assignee: | Backlog - Query Optimization |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | Ideas, debugging | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Participants: |
| Description |
|
When debugging a CQF test on Evergreen, we don't log the final memo by default. You have to add a log statement, enable internalCascadesOptimizerStdCoutDebugOutput, and then find the right place in the log file. Then the multiline output you're interested in can be interleaved with other messages you want to ignore. It would be convenient if you could open/download just the memo, in a separate tab. It would also be good if these were generated by default, so we don't spend a lot of time trying to reproduce rare failures. |
| Comments |
| Comment by David Percy [ 11/Apr/23 ] |
|
We've made other testing improvements since this was proposed so I don't think we need this necessarily. |