[SERVER-60891] Ensure Ninja compile tasks run on suggested builders Created: 21/Oct/21 Updated: 29/Oct/23 Resolved: 03/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ryan Egesdahl (Inactive) | Assignee: | Daniel Moody |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v5.2, v5.0
|
||||
| Sprint: | Dev Platform 2022-02-07 | ||||
| Participants: | |||||
| Description |
|
While working on our latest Ninja changes, we twice had users report problems - on OSX and then on Windows - after pushing our changes. We currently have compile_ninja, the task that would have exercised the changes, running on only one build variant - Enterprise Ubuntu 18.04 - which would have passed had it been run. We only execute compile_ninja_next on Enterprise Ubuntu 18.04, Enterprise Windows DEBUG (Unoptimized), and Enterprise macOS, two of which would have failed if compile_ninja had run instead. We should ensure that both compile_ninja and compile_ninja_next run on -suggested build variants for Windows, OSX, RHEL, and Ubuntu so we have adequate coverage of any changes to the Ninja tool. |
| Comments |
| Comment by Githook User [ 03/Feb/22 ] |
|
Author: {'name': 'Daniel Moody', 'email': 'daniel.moody@mongodb.com', 'username': 'dmoody256'}Message: |