[SERVER-76845] Remove the config_fuzzer_concurrency_sharded_replication suite from the test Windows DEBUG builder Created: 04/May/23 Updated: 29/Oct/23 Resolved: 05/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Execution Team 2023-05-15 | ||||
| Participants: | |||||
| Linked BF Score: | 150 | ||||
| Description |
|
The linked test failure is happening a lot on Windows DEBUG builder only. That particular suite is very slow, and that builder makes it slower, and is also a relatively expensive builder to run. I also recommend removing all the *concurrency_sharded_replication test suites from the builder. It's a known slow builder, where we primarily don't have failures in concurrency suites due to code logic issues, just test failures due to a fundamentally slow concurrency suite running on a machine that has a level of detail that makes things even slower, pushing the timeout boundary frequently. |
| Comments |
| Comment by Githook User [ 05/May/23 ] |
|
Author: {'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}Message: |