[SERVER-26444] Loggers in resmoke.py are sometimes used when no handlers have been set up Created: 03/Oct/16  Updated: 29/Jan/18  Resolved: 02/Jun/17

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

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Duplicate Votes: 0
Labels: neweng, tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

python buildscripts/resmoke.py always_fails.js --log=buildlogger

always_fails.js

throw new Error("bad");

Output

[executor:js_test:job0] 2016-10-03T17:31:58.053-0400 always_fails.js ran in 0.07 seconds.
No handlers could be found for logger "js_test"
[executor:js_test:job0] 2016-10-03T17:31:58.053-0400 Received a StopExecution exception: JSTest always_fails.js failed.
[executor:js_test] 2016-10-03T17:31:58.103-0400 Summary: 1 test(s) ran in 0.12 seconds (0 succeeded, 0 were skipped, 1 failed, 0 errored)


When --log=console (the default value) is used and --continueOnFailure wasn't specified, then we log the following message.

[js_test] 2016-10-03T17:30:21.859-0400 JSTest always_fails.js failed, so stopping...

Participants:

 Description   

We should use the logger of the Job instance instead.



 Comments   
Comment by Yves Duhem [ 02/Jun/17 ]

This issue was fixed as part of the work on SERVER-28991 in the following commit: https://github.com/mongodb/mongo/commit/a4d2c52dbabc323f752776c7c86ac1d8a60187cb

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