Hmm, the tests the fail seems to vary a little between builds.

https://build.chromium.org/p/chromium.fyi/builders/ClangToTWin%28dbg%29%20tester/builds/4562 shows

CrashRecoveryBrowserTest.LoadInNewTab
DevToolsReattachAfterCrashTest.TestReattachAfterCrashOnTimeline
CrashRecoveryBrowserTest.DoubleReloadWithError

as failing.


When I run locally, the tests pass, but I don't get the message about crashing intentionally:

[ RUN      ] DevToolsReattachAfterCrashTest.TestReattachAfterCrashOnTimeline
HTTP server started on http://127.0.0.1:59383...
sending server_data: {"host": "127.0.0.1", "port": 59383} (36 bytes)
[19072:8728:0912/143527.269:ERROR:CONSOLE(22)] "Empty response arrived for script 'chrome-devtools://devtools/remote/serve_file/@9c48e8cf31cb4f4f06d08006ae084f02a7d4261c/product_registry_impl/product_registry_impl_module.js'", source: chrome-devtools://devtools/bundled/inspector.js (22)
[19072:8728:0912/143527.307:ERROR:CONSOLE(105)] "Uncaught (in promise) Error: Could not instantiate: ProductRegistryImpl.Registry", source: chrome-devtools://devtools/bundled/inspector.js (105)
[19072:8728:0912/143527.332:ERROR:CONSOLE(105)] "Uncaught (in promise) Error: Could not instantiate: ProductRegistryImpl.Registry", source: chrome-devtools://devtools/bundled/inspector.js (105)
[19072:8728:0912/143527.347:ERROR:CONSOLE(105)] "Uncaught (in promise) Error: Could not instantiate: ProductRegistryImpl.Registry", source: chrome-devtools://devtools/bundled/inspector.js (105)
[19072:8728:0912/143528.789:WARNING:render_widget_host_impl.cc(275)] Input request on unbound interface
[19072:8728:0912/143528.807:WARNING:render_widget_host_impl.cc(302)] Input request on unbound interface
[19072:8728:0912/143528.815:WARNING:render_widget_host_impl.cc(302)] Input request on unbound interface
[19072:8728:0912/143528.825:WARNING:render_widget_host_impl.cc(302)] Input request on unbound interface
[19072:20944:0912/143530.609:ERROR:process_win.cc(139)] Unable to terminate process: Access is denied. (0x5)
[19072:8728:0912/143530.742:INFO:chrome_cryptauth_service.cc(222)] Profile is not authenticated yet; waiting before starting CryptAuth managers.
[19072:8728:0912/143530.780:ERROR:event_page_request_manager.cc(154)] An error encountered while waking the event page.
[19072:8728:0912/143530.791:ERROR:event_page_request_manager.cc(96)] Draining request queue. (queue-length=3)
[19072:8728:0912/143530.932:WARNING:url_request_context_getter.cc(43)] URLRequestContextGetter leaking due to no owning thread.
[       OK ] DevToolsReattachAfterCrashTest.TestReattachAfterCrashOnTimeline (13125 ms)


Something seems to be flaky here.

This bot continues to be mostly red, with occasional successful runs. I'd like to see if we can figure out what actually causes the failing runs.

One thing that stands out is

5836:3648:0919/054557.613:ERROR:direct_composition_surface_win.cc(1095)] Failing to detect HDR, couldn't retrieve D3D11 device from ANGLE.
[5836:3648:0919/054557.923:INFO:media_foundation_video_encode_accelerator_win.cc(335)] Windows versions earlier than 8 are not supported.

The bot claims it's running Windows 7. If that's not supposed to be supported, we should probably update the OS on the bot. If Windows 7 is supposed to be supported, we probably shouldn't be reporting an error and a "not supported" message here (assuming they are related).

The Chrome website suggests that Windows 7 is supported, so presumably these messages are red herrings and not indicative of a failure reason for these tests.

Yes, those are probably red herrings.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot