[SERVER-56897] libdeps_next broke scanner chaining in its affected builders Created: 12/May/21 Updated: 29/Oct/23 Resolved: 14/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Moody | Assignee: | Daniel Moody |
| 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 |
| Sprint: | Dev Platform 2021-05-17 |
| Participants: |
| Description |
|
A small regression causes the libdeps scanner to not call its underlying target scanners, breaking the scanner call chain, this has limited effect in the mongo build because it affects the SCons scanners looking at the LIBS var and the mongo build uses mostly LIBDEPS in place of that. |
| Comments |
| Comment by Githook User [ 13/May/21 ] |
|
Author: {'name': 'Daniel Moody', 'email': 'daniel.moody@mongodb.com', 'username': 'dmoody256'}Message: |