[SERVER-52794] scons compiledb is always rebuilt even when nothing changed Created: 11/Nov/20 Updated: 27/Oct/23 Resolved: 27/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0 Desired |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Moody | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Development Platform
|
| Operating System: | ALL |
| Steps To Reproduce: | build compiledb use ls to check the timestamp of compile_commands.json build compiledb again after a min use ls to check timestamp of compile_commands.json is now different. |
| Participants: |
| Description |
|
This may be more trouble then its worth, or maybe is part of the design of the compiledb scons tool, but the compiledb is always rebuilt even when nothing is changed.
|
| Comments |
| Comment by Andrew Morrow (Inactive) [ 04/Jan/21 ] |
|
Well, "by design" might be a strong claim, but it is explicitly declared AlwaysBuild: https://github.com/mongodb/mongo/blob/f012be046c8a16fe80ca3c08ee19a48931feb696/site_scons/site_tools/compilation_db.py#L202. We could do some archaeology to try to discover why, but it has been there since the original implementation under |