[SERVER-81001] burn_in_tests does not correctly determine which suites to run for a specific test Created: 12/Sep/23 Updated: 02/Nov/23 Resolved: 02/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Trevor Guidry | Assignee: | [DO NOT ASSIGN] Backlog - DevProd Correctness |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Correctness
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
Possibly a duplicate/related to https://jira.mongodb.org/browse/SERVER-80220 burn_in_tests incorrectly runs the test jstests/sharding/timeseries_change_stream_no_orphans.js with the sharding_last_continuous suite when it should be excluded and resmoke errors out saying that it cannot run an excluded test. This probably has something to do with feature flags not working as intended. An example patch build can be seen here https://spruce.mongodb.com/version/64ff266ad6d80abb708a6733
Original slack thread: https://mongodb.slack.com/archives/C0V79S1PY/p1694543626586979 |