[SERVER-82601] Consider raising timeout on TSAN noPassthrough evergreen task Created: 30/Oct/23 Updated: 02/Jan/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Erin McNulty | Assignee: | [DO NOT ASSIGN] Backlog - DevProd Correctness |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Correctness
|
| Participants: |
| Description |
|
While working on BF-30427, I identified and fixed a true data race, and filed tickets for the others. However, I it was hard to reliably test the noPassthrough task without hitting the timeout, and I raised the timeout to 3 hours for the duration of my testing, which I found allowed the tests to reliably complete under the time limit. I think it may be worthwhile to permanently increase this time limit in order to reduce the flakiness of the TSAN testing. |