[SERVER-62236] Address novel warnings produced when building in with MSVS 2022 Created: 22/Dec/21 Updated: 27/Oct/23 Resolved: 13/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Development Platform
|
||||||||
| Sprint: | Dev Platform 2022-01-24 | ||||||||
| Participants: | |||||||||
| Description |
|
If any new warnings are produced with MSVS 2022, address them either with code fixes or minimally targeted warning suppression flags. Once all warnings are removed, update the experimental builders using MSVS 2022 to build without --disable-warnings-as-errors. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 13/Jan/22 ] |
|
No novel warnings were encountered that needed repair; closing. |
| Comment by Andrew Morrow (Inactive) [ 11/Jan/22 ] |
|
I'm blocking this ticket on |