[SERVER-31556] Fix ContinuousStepdown logger Created: 13/Oct/17  Updated: 30/Oct/23  Resolved: 26/Nov/17

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.6.4, 3.7.1

Type: Bug Priority: Major - P3
Reporter: Ian Boros Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Problem/Incident
causes SERVER-32474 resmoke.py logging output from data c... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6
Sprint: TIG 2017-10-23, TIG 2017-11-13, TIG 2017-12-04
Participants:

 Description   

In patch builds using the ContinuousStepdown hook, we usually see:

No handlers could be found for logger "ContinuousStepdown:job0"

We should fix this, so that we can see the log messages printed by the hook.



 Comments   
Comment by Githook User [ 10/Mar/18 ]

Author:

{'email': 'max.hirschhorn@mongodb.com', 'name': 'Max Hirschhorn', 'username': 'visemet'}

Message: SERVER-31556 Use fixture logger as parent of hook logger.

This enables the hook logger to log messages to logkeeper when
--log=buildlogger is specified without needing to start a new dynamic
test case.

(cherry picked from commit 611220640b0fd32fcf81f47cdae6882a26bbac0b)
Branch: v3.6
https://github.com/mongodb/mongo/commit/bb6a79ebab7b737d72b370dcd815cc15b554b559

Comment by Githook User [ 26/Nov/17 ]

Author:

{'name': 'Max Hirschhorn', 'username': 'visemet', 'email': 'max.hirschhorn@mongodb.com'}

Message: SERVER-31556 Use fixture logger as parent of hook logger.

This enables the hook logger to log messages to logkeeper when
--log=buildlogger is specified without needing to start a new dynamic
test case.
Branch: master
https://github.com/mongodb/mongo/commit/611220640b0fd32fcf81f47cdae6882a26bbac0b

Generated at Thu Feb 08 04:27:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.