Closed Bug 1261812 Opened 9 years ago Closed 8 years ago

Ensure Windows build/test machines have Windows Error Reporting configured to write local dumps, but suppress WER UI

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ted, Unassigned)

Details

Attachments

(1 file)

Bruce Dawson (a Googler) tweeted a link to a change he made in Chromium's Windows builder setup: https://codereview.chromium.org/1825163003/diff/60001/win_toolchain/get_toolchain_if_necessary.py Setting those two registry keys ensures that Windows Error Reporting will write minidumps to a local folder (%LOCALAPPDATA%\CrashDumps), but not display the crash dialog (which tends to hang things in automation). We should ensure that those two registry keys are set on our Windows build and test machines, so we're not getting unnecessary crash dialogs, but are getting minidumps that are useful for diagnosing unhandled crashes.
Added to cloud-tools windows userdata
Attachment #8738149 - Flags: feedback?(mcornmesser)
Attachment #8738149 - Flags: feedback?(mcornmesser) → feedback+
Still needed?
Flags: needinfo?(ted)
Sounds like grenade fixed this for Taskcluster workers, so that should be sufficient.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(ted)
Resolution: --- → FIXED
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: