Issue metadata
Sign in to add a comment
|
Re-implement thread backtrace dumps for hung TestLauncher sub-processes |
||||||||||||||||||||||
Issue descriptionWe use the system-provided 'threads' utility to dump the stacks of all threads in a hung TestLauncher batch process, to help diagnose the cause of test hangs. This was broken by the migration to packages, presumably because 'threads' isn't being explicitly made available to the test package now.
,
Jun 5 2018
,
Jun 7 2018
,
Jun 7 2018
,
Jul 17
,
Jul 26
,
Jul 26
,
Jul 27
This is now blocked-on bug DX-185, for exposing a remote process/thread stack unwinding helper library.
,
Aug 2
,
Aug 3
,
Sep 1
,
Sep 4
,
Sep 10
,
Sep 11
,
Sep 24
The NextAction date has arrived: 2018-09-24
,
Oct 15
,
Nov 4
The NextAction date has arrived: 2018-11-04
,
Nov 5
,
Dec 2
The NextAction date has arrived: 2018-12-02
,
Dec 14
,
Jan 7
The NextAction date has arrived: 2019-01-07
,
Jan 19
(4 days ago)
Closing this out since we now have Run() timeout stacks, which are better than nothing. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kmarshall@chromium.org
, May 9 2018