[SERVER-53788] Add an agg-fuzzer flag to make reproducing agg fuzzer failures easier Created: 14/Jan/21 Updated: 06/Dec/22 Resolved: 24/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ted Tuckman | Assignee: | Backlog - Query Optimization |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | quick-tech-debt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query Optimization
|
||||
| Participants: | |||||
| Description |
|
The idea of this ticket would be to save time when debugging fuzzer failures. If we could figure out a way for the server to communicate which document caused an error (either in the error message body, log, or some other way), the fuzzer could log the document when discrepancies are detected. This would shorten repro time considerably. I'm not 100% sure how we would do this. Its possible adding context to the error assertions when a flag is on would be enough, but would have to investigate further. |
| Comments |
| Comment by Charlie Swanson [ 24/Sep/21 ] |
|
In absence of any more specific idea and with a bunch of other "nice-to-have" tickets lying around. We'll close this one. If any ideas come up, please open a new ticket! |
| Comment by Charlie Swanson [ 28/Jan/21 ] |
|
Just wanted to point out that this is related to PM-1880. That's an entire project/epic, so probably we're looking for something much more targeted and quick-and-easy with this ticket. |