[SERVER-54814] Fall back to default config file location for Evergreen API config in burn_in_tests.py Created: 26/Feb/21 Updated: 29/Oct/23 Resolved: 25/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | David Bradford (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | DAG 2021-04-05 |
| Participants: | |
| Story Points: | 2 |
| Description |
Motivation for RequestContextDescriptionThe --evg-api-config option to burn_in_tests.py has its own default value that's different to the default value in evergreen.py. The latter is friendlier for local invocations; consider adding it as a fallback for burn_in_tests.py (or using it as the default for burn_in_tests, replacing the current value) would benefit users trying to run burn_in_tests.py locally. See original request here on the Server wiki |
| Comments |
| Comment by Githook User [ 25/Mar/21 ] |
|
Author: {'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}Message: |
| Comment by David Bradford (Inactive) [ 02/Mar/21 ] |
|
Running `burn_in_tests` locally shouldn't even need to use the evergreen-api. So what is specified in that option should be irrelevant. It does look like it fails running locally if the file isn't found, we should fix that and clean up the interface. |