[SERVER-54253] ninja tool should process content signatures for subst expansions Created: 03/Feb/21  Updated: 27/Oct/23  Resolved: 27/Oct/23

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

Type: New Feature Priority: Minor - P4
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
Participants:

 Description   

The ninja tool ignores content signatures generated by subst expansions. Normally this is not a problem because most subst expansions don't produce a different content signature from their own expansion, but in some cases (like SERVER-49299) the user will provide an alternate content signature from the expansion. 

 

This means ninja will incorrectly not rebuild certain items because it lacks information regarding a subst expansion. Possibly ninja could re-perform the subst expansion for signature checking to determine if it needs to rebuild by extracting the python code in some form and running it in a scons context. It would be hard.



 Comments   
Comment by Daniel Moody [ 21/Mar/22 ]

related discussion: https://github.com/SCons/scons/issues/3624

Generated at Thu Feb 08 05:33:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.