[SERVER-37104] Unit testing framework has become dependent on service_context Created: 12/Sep/18 Updated: 29/Oct/23 Resolved: 13/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Sara Golemon |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Security 2018-09-24 |
| Participants: |
| Description |
|
The mongo/unittest/unittest library links to mongo/options_parser/options_parser, which has recently picked up a dependency on mongo/util/net/http_client. That library, in turn, links to mongo/executor/thread_pool_task_executor, which, ultimately, links in mongo/db/service_context. As a result, all unit tests now link the service_context code and its semi-extensive transitive dependencies, whether they need it or not. We should find a way to not make the options subsystem (or the http subsystem) force this dependency into all unit tests. |
| Comments |
| Comment by Githook User [ 13/Sep/18 ] |
|
Author: {'name': 'Sara Golemon', 'email': 'sara.golemon@mongodb.com', 'username': 'sgolemon'}Message: |