-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
Trivial - P5
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
It looks like recent master builds of mongod are not respecting the backtraceLogFile parameter and this is causing some js tests to fail:
% ./build/install/bin/mongod --setParameter backtraceLogFile=/dev/null {"t":{"$date":"2022-07-18T16:06:43.508Z"},"s":"F", "c":"CONTROL", "id":20574, "ctx":"main","msg":"Error during global initialization","attr":{"error":{"code":2,"codeName":"BadValue","errmsg":"Unknown --setParameter 'backtraceLogFile'"}}}
In the resmoke js-test context:
% python buildscripts/resmoke.py run -j4 --installDir=~/mongo/build/debug/install/bin jstests/sharding/allow_partial_results.js ... [js_test:allow_partial_results] c20043| 2022-07-18T11:11:29.688-0500 F CONTROL [main] Failed global initialization: BadValue: Unknown --setParameter 'backtraceLogFile' [js_test:allow_partial_results] d20041| 2022-07-18T11:11:29.703-0500 F CONTROL [main] Failed global initialization: BadValue: Unknown --setParameter 'backtraceLogFile' [js_test:allow_partial_results] c20042| 2022-07-18T11:11:29.705-0500 F CONTROL [main] Failed global initialization: BadValue: Unknown --setParameter 'backtraceLogFile' [js_test:allow_partial_results] d20040| 2022-07-18T11:11:29.715-0500 F CONTROL [main] Failed global initialization: BadValue: Unknown --setParameter 'backtraceLogFile'
In jira I only saw BF-25861 that is indirectly tracking this.