[SERVER-36357] Add ability to express different log component verbosities in YAML suites depending on whether suite is run in Evergreen or not Created: 30/Jul/18 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.1 Desired |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | stm, tig-qwin-eligible, tig-resmoke | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Tooling & Methods
|
||||||||
| Participants: | |||||||||
| Description |
|
We can currently specify the default log verbosity settings based on whether we are running it in evergreen or not. However, there is no way to that we can set different verbosity settings in YAML suites depending on whether the suite is running locally or in Evergreen. As point out by max.hirschhorn here, this would be helpful as an extension of |
| Comments |
| Comment by Tess Avitabile (Inactive) [ 31/Jul/18 ] |
|
Additionally, we would like to be able to just override the verbosity level for a particular log component in the YAML suites, so that you don't have to re-specify the verbosity level for every log component when you want to change one component for a suite. max.hirschhorn, we'll assign this feature request to the TIG backlog. This would be valuable for the replication team. |