[SERVER-48022] Cleanup infrastructure log lines in mongo/util Created: 07/May/20  Updated: 29/Oct/23  Resolved: 01/Jun/20

Status: Closed
Project: Core Server
Component/s: Diagnostics, Logging
Affects Version/s: None
Fix Version/s: 4.4.0-rc8, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Benjamin Caimano (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Service arch 2020-06-01, Service arch 2020-06-15
Participants:

 Description   

A survey of log files produced by running tests in Evergreen showed some potential problems with messages originating from these files.

src/mongo/util/options_parser/options_parser.cpp
src/mongo/util/signal_handlers.cpp
src/mongo/util/signal_handlers_synchronous.cpp
src/mongo/util/stacktrace_threads.cpp

ben.caimano I'm not sure if these were meant to be addressed by SERVER-47076, but I wonder if you could take a look to see if more work could be done in these files, and/or help me figure out who should look?



 Comments   
Comment by Githook User [ 01/Jun/20 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-48022 Cleanup infrastructure log lines in mongo/util
Branch: v4.4
https://github.com/mongodb/mongo/commit/e0e3700b61c663acfb9647f1d99f66fa1ac83190

Generated at Thu Feb 08 05:15:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.