On win_chromium_x64_rel_ng and win_chromium_rel_ng at the least, stack traces for test failures display as follows:

	GetHandleVerifier [0x0000000140CFED81+46513]
	(No symbol) [0x0000000140CAEC7C]
	(No symbol) [0x00000001404C5719]
	(No symbol) [0x00000001404C5D8D]
	(No symbol) [0x000000013FF2156D]
	(No symbol) [0x000000013FF1DE93]
	(No symbol) [0x000000013FF00672]
	(No symbol) [0x000000013FEB02E7]
	(No symbol) [0x000000013FB307E4]
	(No symbol) [0x000000013FB30613]
	(No symbol) [0x000000013FAFAA94]
	(No symbol) [0x000000013FB035CE]
	GetHandleVerifier [0x0000000140D65B51+467841]
	GetHandleVerifier [0x0000000140D73256+522886]
	GetHandleVerifier [0x0000000140D73475+523429]
	GetHandleVerifier [0x0000000140D7335D+523149]
	GetHandleVerifier [0x0000000140D7381B+524363]
	GetHandleVerifier [0x0000000140D65BF1+468001]
	GetHandleVerifier [0x0000000140D735B5+523749]
	(No symbol) [0x000000013FB576ED]
	(No symbol) [0x000000013FB6CDC3]
	(No symbol) [0x000000013FB6C9C0]
	(No symbol) [0x000000013FAF5791]
	GetHandleVerifier [0x000000014102B83C+3375212]
	BaseThreadInitThunk [0x00000000777C59CD+13]
	RtlUserThreadStart [0x00000000778FB891+33]

This suggests the symbolizer isn't working.

Failing runs where this occurs:
https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_rel_ng/builds/220708

https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_ng/builds/229247