Identify the hung thread using the Wait Chain Traversal API

chrome/test/kasko/hang_watcher_integration_test.py

 #!/usr/bin/env python
 # Copyright 2016 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 """A Windows-only end-to-end integration test for the Chrome hang watcher.
 
 This test ensures that the hang watcher is able to detect when Chrome hangs and
 to generate a Kasko report. The report is then delivered to a locally hosted
 test crash server. If a crash report is received then all is well.
 
 Note that this test only works against non-component Release and Official builds
 of Chrome with Chrome branding, and attempting to use it with anything else will
 most likely lead to constant failures.
 
 Typical usage (assuming in root 'src' directory):
 - generate project files with the following build variables:
     GYP variables:
-      branding=Chrome kasko=1 kasko_hang_reports=1
+      branding=Chrome kasko_hang_reports=1
     GN variables:
       target_cpu = "x86"
       is_debug = false
       is_chrome_branded = true
-      enable_kasko = true
       enable_kasko_hang_reports = true
 - build the release Chrome binaries:
     ninja -C {build_dir} chrome.exe chromedriver.exe
 - run the test:
     python chrome/test/kasko/hang_watcher_integration_test.py
       --chrome={build_dir}\chrome.exe
 """
 
 import logging
 import os
@@ skipping 16 matching lines @@
                                  120,
                                  {'hung-process': 'DumpHungBrowserProcess()'})
 
   _LOGGER.info('Test passed successfully!')
 
   return 0
 
 
 if __name__ == '__main__':
   sys.exit(Main())