Assigning to dpranke@ for more investigation based on the content_shell_crash_test.py blame list.
Dirk, please feel free to re-assign if necessary.

I don't know which build this was failing in, or which blamelist you thought I might be a part of?

Looking at https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win10%20Tests%20x64%20%28dbg%29?limit=200 I see this test step has been failing off and on for some time.

pennymac@, can I punt this to you to triage / re-punt ?

Hey Dirk, I'm not the best person to figure out owners for bug tickets.  E.g. I have no idea who would be best for a content test failure.

My best advice is to set the OS to Windows on these tickets, add detail about this situation of a brand new DBG bot with flaky results, set Status to Untriaged, and make sure it's linked from the parent tracking ticket.  Then I think our existing triage processes should kick in?!

(If I'm wrong on the "triage systems", please let me know.  I don't claim to be an expert.)

@scottmg to triage content_shell_crash_test flakes on Windows 

Example flake @ https://chromium-swarm.appspot.com/task?id=3d8c8b3423505910&refresh=10&show_raw=1

DevTools listening on ws://127.0.0.1:62358/devtools/browser/7aa871d7-e354-478e-a19b-04dcc3c9994f
#CRASHED - renderer
[8628:936:0518/074935.670:WARNING:discardable_shared_memory_manager.cc(431)] Some MojoDiscardableSharedMemoryManagerImpls are still alive. They will be leaked.
#CRASHED - renderer
# Running test without trap handler.
# Run content_shell and make it crash.
.\content_shell.exe --run-web-tests chrome://crash --enable-crash-reporter --crash-dumps-dir=c:\b\s\w\itbwpgbj\tmpw0mufj
# Retrieve crash dump.
FAIL: Expected 1 crash dump, found 0.

 Issue 846313  has been merged into this issue.

Hmm, sounds very similar but  Issue 846313  succeeds at "# Retrieve crash dump." and fails at the next step.

Issues  846313  highlighted this log :

Command: e:\b\s\w\ir\.swarming_module_cache\vpython\ba88f3\Scripts\python.exe e:\b\s\w\ir\content\shell\tools\breakpad_integration_test.py --verbose --build-dir . --binary .\content_shell.exe --json e:\b\s\w\itjubc56\tmp9torzk
#READY
DevTools listening on ws://127.0.0.1:62896/devtools/browser/8cb2aa74-efdc-4eb9-bcf6-2c67ab14a829
[6816:4996:0523/085416.878:ERROR:render_frame_impl.cc(886)] Intentionally crashing (with null pointer dereference) because user navigated to chrome://crash/
#CRASHED - renderer
#CRASHED - renderer
# Running test without trap handler.
# Run content_shell and make it crash.
.\content_shell.exe --run-web-tests chrome://crash --enable-crash-reporter --crash-dumps-dir=e:\b\s\w\itjubc56\tmpkimkk7
# Retrieve crash dump.
# Symbolize crash dump.
.\cdb\cdb.exe -y . -c .lines;.excr;k30;q -z e:\b\s\w\itjubc56\tmpkimkk7\reports\f1f0ceba-0f86-43c5-809a-2510f6cb97d3.dmp
FAIL: Could not find reference to CrashIntentionally in stack.

Here's the regression range for https://ci.chromium.org/buildbot/chromium.win/Win7%20Tests%20%281%29/?limit=200 :

https://chromium.googlesource.com/chromium/src/+log/bee4a5a94f7ea8942a6b51200be99076d4db57eb..b7a3fd5d28f223b18d5d8660aa57ce190678b921?pretty=fuller&n=10000

I suspect r561063 which touched toolchain related build files.

https://chromium-review.googlesource.com/c/chromium/src/+/1072307

Actually bots are green on OP, dedupping back  issue 846313 .