[SERVER-27955] scons cache pruning script deletes cache config Created: 08/Feb/17 Updated: 27/Oct/23 Resolved: 29/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Sam Kleinman (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Platforms 2017-04-17 |
| Participants: |
| Description |
|
currently the scons cache pruning script deletes the cache config file because it is not updated regularly ($CACHE_DIR/config) However, this file should never be deleted. We don't run into this on our ephemeral systems because they are not long-lived enough to ever hit this issue, but any attempt to share and prune the cache between builds will lead to corrupted caches, missing the config file. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 29/Mar/17 ] |
|
The cache prune script only looks inside sub-directories of the cache dir for files to prune, so it does not appear that it could have removed the config file. |