[SERVER-80679] Improve optimizer gdb tests to verify printed output Created: 01/Sep/23 Updated: 08/Jan/24 Resolved: 08/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Nicholas Zolnierz |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QO 2023-09-04, QO 2023-09-18, QO 2023-10-02, QO 2023-10-16, QO 2023-10-30, QO 2023-11-13, QO 2023-11-27, QO 2023-12-11, QO 2023-12-25, QO 2024-01-08 |
| Participants: |
| Description |
|
Currently, the optimizer gdb tests only assert that we're able to lookup the types in the mongod binary. It would be better to do this and also assert that the pretty printed output is stable, likely with a dummy program that forces a breakpoint and has several types in scope (e.g. see here for an example). |
| Comments |
| Comment by Githook User [ 08/Jan/24 ] |
|
Author: {'name': 'Nick Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com', 'username': 'nzolnierzmdb'}Message: GitOrigin-RevId: f7d8e7c396067c7254bf7b0b4fc1ea4370cfec6c |
| Comment by Githook User [ 14/Dec/23 ] |
|
Author: {'name': 'Sara Golemon', 'email': 'sara.golemon@mongodb.com', 'username': 'sgolemon'}Message: GitOrigin-RevId: 8547cb56b26cdba17cde0372c2491b2dc4a8d553 |