fe0d5c7ca8
Reason for revert:
CHECK is too strict.
Original issue's description:
> [inspector] use creation stack trace as parent for async call chains
>
> Creation stack trace points to the place where callback was actually chained, scheduled points where parent promise was resolved.
> For async tasks without creation stack (e.g. setTimeout) we continue to use scheduled as creation since usually they are the same.
>
> BUG=v8:6189
> R=dgozman@chromium.org
>
> Review-Url: https://codereview.chromium.org/2868493002
> Cr-Commit-Position: refs/heads/master@{#45198}
> Committed: e118462f18
TBR=dgozman@chromium.org,alexclarke@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:6189
Review-Url: https://codereview.chromium.org/2868423004
Cr-Commit-Position: refs/heads/master@{#45242}
44 lines
714 B
Plaintext
44 lines
714 B
Plaintext
Checks async instrumentation enabled in the middle.
|
|
|
|
Running test: beforeAsyncTaskScheduled
|
|
test (test.js:16:2)
|
|
(anonymous) (expr1.js:0:0)
|
|
|
|
test (test.js:21:2)
|
|
(anonymous) (expr1.js:0:0)
|
|
|
|
foo (test.js:10:2)
|
|
-- Promise.resolve --
|
|
test (test.js:20:2)
|
|
(anonymous) (expr1.js:0:0)
|
|
|
|
foo (test.js:12:2)
|
|
-- Promise.resolve --
|
|
test (test.js:20:2)
|
|
(anonymous) (expr1.js:0:0)
|
|
|
|
|
|
Running test: afterAsyncTaskScheduled
|
|
test (test.js:16:2)
|
|
(anonymous) (expr1.js:0:0)
|
|
|
|
test (test.js:21:2)
|
|
(anonymous) (expr1.js:0:0)
|
|
|
|
foo (test.js:10:2)
|
|
|
|
foo (test.js:12:2)
|
|
|
|
|
|
Running test: afterAsyncTaskStarted
|
|
test (test.js:16:2)
|
|
(anonymous) (expr1.js:0:0)
|
|
|
|
test (test.js:21:2)
|
|
(anonymous) (expr1.js:0:0)
|
|
|
|
foo (test.js:10:2)
|
|
|
|
foo (test.js:12:2)
|
|
|