[SERVER-69268] Disable bypass compile during burn_in_tags_gen Created: 31/Aug/22 Updated: 29/Oct/23 Resolved: 02/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.23, 4.4.17 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jeffrey Zambory | Assignee: | Jeffrey Zambory |
| 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: |
v4.4, v4.2
|
||||||||||||
| Sprint: | DAG 2022-09-05 | ||||||||||||
| Participants: | |||||||||||||
| Story Points: | 1 | ||||||||||||
| Description |
|
Currently, burn_in tags is generating tasks that allow for their compile steps to be bypassed and for them to retrieve their compiled code from a previous task. Bypass_compile in general has been brittle and has led to odd behavior at times. We disabled bypass_compile for most cases as part of https://jira.mongodb.org/browse/SERVER-50078. We should remove this step as well from burn_in_tags to make it consistent across the board. |
| Comments |
| Comment by Githook User [ 01/Sep/22 ] |
|
Author: {'name': 'Jeff Zambory', 'email': 'jeff.zambory@mongodb.com'}Message: (cherry picked from commit 478c4385575e231782a555b1691696167ddff1d3) |
| Comment by Githook User [ 01/Sep/22 ] |
|
Author: {'name': 'Jeff Zambory', 'email': 'jeff.zambory@mongodb.com'}Message: |