[SERVER-48150] Streamline resmoke loggers Created: 12/May/20 Updated: 29/Oct/23 Resolved: 17/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Raiden Worley (Inactive) | Assignee: | Raiden Worley (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tig-resmoke | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | STM 2020-06-15, STM 2020-06-29 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||||||
| Description |
|
We currently construct JobLoggers from ExecutorRootLogger instances, creating a weird situation where they use some information from ExecutorRootLogger and some information from FixtureRootLogger. After changing how logging configuration is managed, we should be able to construct JobLoggers directly in Job objects. |
| Comments |
| Comment by Githook User [ 17/Jun/20 ] |
|
Author: {'name': 'Carl Raiden Worley', 'email': 'carl.worley@10gen.com', 'username': 'aggrand'}Message: |
| Comment by Raiden Worley (Inactive) [ 09/Jun/20 ] |
|
Turns out that constructing the joblogger directly in the job object doesn't make sense, because the job logger is needed in the TestReport constructor in the executor. Instead, I'm using this ticket to flatten the class hierarchy. |