[SERVER-61432] symbolizer should not change global logging config Created: 12/Nov/21 Updated: 29/Oct/23 Resolved: 24/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Jasur Nurboev (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | evergreen-yaml | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | DAG 2022-10-31 | ||||||||
| Participants: | |||||||||
| Story Points: | 1 | ||||||||
| Description |
|
Timebox: 1 day |
| Comments |
| Comment by Githook User [ 24/Oct/22 ] | ||||
|
Author: {'name': 'jasurbeknurboyev', 'email': '998946972365'}Message: | ||||
| Comment by Robert Guo (Inactive) [ 17/Oct/22 ] | ||||
|
iryna.zhuravlova@mongodb.com jasur.nurboev@mongodb.com yep. Here's the place that we're setting the global logging config. The productionized approach is to create a dedicated logger. Here's how we do it in the hang analyzer | ||||
| Comment by Iryna Zhuravlova [ 17/Oct/22 ] | ||||
|
hey robert.guo@mongodb.com can you help us (jasur.nurboev@mongodb.com) to identify where this might be coming from? | ||||
| Comment by Max Hirschhorn [ 17/Aug/22 ] | ||||
|
Re-opening this ticket because it is still incorrect to use logging.basicConfig() to globally change the log settings for the current resmoke Python process. It causes the test output to end up showing up in the task logs.
| ||||
| Comment by Robert Guo (Inactive) [ 03/Jun/22 ] | ||||
|
Thanks for the reminder sviatlana.zuiko@mongodb.com; I had missed the connection between the two issues. Checking the code just now, Misha refactored the code 2 weeks ago here to call out to the db-contrib-tool subprocess, so logging config should no longer impact anything else in resmoke. Could you let me know if you are still seeing the issue? It might be a bug elsewhere. | ||||
| Comment by Sviatlana Zuiko [ 31/May/22 ] | ||||
|
robert.guo@mongodb.com, do I understand correctly that this issue caused test logs being merged in task logs? | ||||
| Comment by Robert Guo (Inactive) [ 27/May/22 ] | ||||
|
No longer a priority after db-contrib-tool was refactored | ||||
| Comment by Robert Guo (Inactive) [ 26/Apr/22 ] | ||||
|
Could we park this under a label for tech debt? Not urgent IMO |