Bug 1896767 [wpt PR 46266] - Check thread id is in current frames, a=…

…testonly

Automatic update from web-platform-tests
Check thread id is in current frames (#46266)

On Chromium Windows bot, we are seeing KeyError below. Check the thread
id is in sys._current_frames() before format_stack, otherwise do not
include the stack in the error message.

Error message:
00:02:16.943 WARNING: Exception in TestExecutor.run:
  File "C:\b\s\w\ir\third_party\wpt_tools\wpt\tools\wptrunner\wptrunner\executors\base.py", line 219, in run
    message += "".join(traceback.format_stack(sys._current_frames()[executor.ident]))
KeyError: 8372
--

wpt-commits: c55cca3cabaa78d029191694e7efaff229f9c0a7
wpt-pr: 46266

testing/web-platform/tests/tools/wptrunner/wptrunner/executors/base.py

@@ -215,8 +215,10 @@ def run(self):
             else:
                 if self.protocol.is_alive():
                     message = "Executor hit external timeout (this may indicate a hang)\n"
-                    # get a traceback for the current stack of the executor thread
-                    message += "".join(traceback.format_stack(sys._current_frames()[executor.ident]))
+                    if executor.ident in sys._current_frames():
+                        # get a traceback for the current stack of the executor thread
+                        message += "".join(traceback.format_stack(
+                            sys._current_frames()[executor.ident]))
                     self.result = False, ("EXTERNAL-TIMEOUT", message)
                 else:
                     self.logger.info("Browser not responding, setting status to CRASH")