[SERVER-45358] Retrying all commands in tests if there are background operations is cumbersome when behavior is not desired Created: 03/Jan/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ted Tuckman | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Sprint: | Execution Team 2020-03-23 |
| Participants: |
| Description |
|
This line makes all tests retry operations if there is a background operation in progress. This means that for tests that don't want this behavior, those commands need to be run in parallel shells. It would be useful to have a way to disable this behavior. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 16/Jan/20 ] |
|
The parallel shell bypass can be seen here. I propose using TestData to optionally bypass the implicit background operation in progress error retry functionality for a test. Though we should check out the scope of this solution: I do not know if there are situations where changing TestData manually in one test might affect other running tests? |