[SERVER-42409] Enable WER for CI builds Created: 25/Jul/19 Updated: 06/Dec/22 Resolved: 16/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | move-stm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Server Tooling & Methods
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 55 | ||||||||||||||||
| Description |
|
Our reliance on minidump generation from within the same process is known to be unreliable, per BF-11043. We are also blind to fail fast errors without WER (Windows Error Reporting). We should figure out how to turn on WER in our CI builds at least to help with Windows build failure diagnosis. |
| Comments |
| Comment by Robert Guo (Inactive) [ 16/Nov/20 ] |
|
After reviewing our recent stakeholder requests, I'm not seeing a lot of requirements for gathering diagnostics info on Windows. If improving the development experience on Windows experience is something you'd like to see, please feel free to add it to the next dev-prod stakeholder doc and we can discuss the goal at a higher level. For now, I'm going to close out this ticket. |
| Comment by Brooke Miller [ 10/Mar/20 ] |
|
Based on a conversation with the STM Team, sara.williamson, this is something that we'd like to send back to dev tools. |