[SERVER-68111] backtraceLogFile parameter is not recognized Created: 18/Jul/22 Updated: 18/Jul/22 Resolved: 18/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Trivial - P5 |
| Reporter: | Steve Tarzia | Assignee: | Steve Tarzia |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
It looks like recent master builds of mongod are not respecting the backtraceLogFile parameter and this is causing some js tests to fail:
In the resmoke js-test context:
In jira I only saw BF-25861 that is indirectly tracking this. |
| Comments |
| Comment by Steve Tarzia [ 18/Jul/22 ] |
|
Actually, this was not a bug but user error on my part. There was a mismatch between what I was building and what I was testing. In other words, I was building to build/install/debug/bin but testing build/install/bin. Sorry for the noise! |
| Comment by Billy Donahue [ 18/Jul/22 ] |
|
FTR this feature was introduced by Security team. Service arch had nothing to do with it. |
| Comment by Steve Tarzia [ 18/Jul/22 ] |
|
Actually, based on feedback in a slack thread, I think this is just happening in my environment, not universally. I am lowering the priority and assigning to myself. |
| Comment by Steve Tarzia [ 18/Jul/22 ] |
|
I saw this on commit f14733fccae6676c1871bf0565ebff9a441f9640 |