e69505242f
The test occasionally times out, and it's unclear why.
This CL adds an explicit timeout to the test (30 seconds), and prints
all seen profiles after that. This makes it easier to see which frame is
missing from the profiles.
As a drive-by refactoring, we now also use
{InspectorTest.runAsyncTestSuite} instead of the hand-written sequential
execution of the asynchronous test functions.
R=thibaudm@chromium.org
Bug: v8:13370
Change-Id: I67f53a819706c8e5971bf32dc925d90b21c96243
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3956976
Commit-Queue: Clemens Backes <clemensb@chromium.org>
Reviewed-by: Thibaud Michaud <thibaudm@chromium.org>
Cr-Commit-Position: refs/heads/main@{#83748}
|
||
|---|---|---|
| .. | ||
| console-profile-asm-js-expected.txt | ||
| console-profile-asm-js.js | ||
| console-profile-end-parameterless-crash-expected.txt | ||
| console-profile-end-parameterless-crash.js | ||
| console-profile-expected.txt | ||
| console-profile-wasm-expected.txt | ||
| console-profile-wasm.js | ||
| console-profile.js | ||
| coverage-block-expected.txt | ||
| coverage-block.js | ||
| coverage-expected.txt | ||
| coverage.js | ||
| enable-disable-expected.txt | ||
| enable-disable.js | ||
| record-cpu-profile-expected.txt | ||
| record-cpu-profile.js | ||
| stop-without-preceeding-start-expected.txt | ||
| stop-without-preceeding-start.js | ||