[SERVER-28888] libdeps dependency order unstable without --implicit-cache Created: 20/Apr/17 Updated: 30/Oct/23 Resolved: 21/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Steps To Reproduce: | Build any target without - |
| Sprint: | Platforms 2017-05-08 |
| Participants: |
| Description |
|
In That caused the dependency orders to change run-to-run, unless you were building with --implicit-cache. Since most users do build that way, we didn't notice. The solution is to simply append the results in the stable order returned by __get_libdeps. |
| Comments |
| Comment by Githook User [ 21/Apr/17 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}Message: Also, a quick fix to eliminate a needless sort, since Node.sources |