[SERVER-48147] Remove FallbackLogger Created: 12/May/20 Updated: 01/Feb/21 Resolved: 01/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Raiden Worley (Inactive) | Assignee: | Julian Edwards |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Evergreen 2020-10-05, Evergreen 2020-10-19, Evergreen 2020-11-02, Evergreen 2020-11-16, Evergreen 2020-11-30, Evergreen 2020-12-14, Evergreen 2021-01-25, Evergreen 2021-02-08 |
| Participants: | |
| Story Points: | 2 |
| Description |
|
The current buildlogger implementation has a fallback logger that logs to stderr in cases where buildlogger itself is failing. Fallback logger is no longer needed after we use Jasper for logging, so it should be removed. |
| Comments |
| Comment by Julian Edwards [ 01/Feb/21 ] |
|
Since we are not planning on using jasper/cedar logging in resmoke for all variants, I am going to close this ticket. It is my understanding that as long as there is a dependency on logkeeper v2, the fallback logger should exist. robert.guo feel free to reopen if this is not the case. |
| Comment by Iryna Zhuravlova [ 25/Jan/21 ] |
|
This will be the last the last ticket in the project to clean up the code. |