[SERVER-50312] Don't save UndoDB recordings for successful fixtures. Created: 14/Aug/20 Updated: 06/Dec/22 Resolved: 29/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Richard Samuels (Inactive) | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | tig-resmoke | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Tooling & Methods
|
||||
| Participants: | |||||
| Story Points: | 2 | ||||
| Description |
|
We currently save recordings based on resmoke return code. Instead, delete recordings when the fixture the recording corresponds to is successful |