|
|
Created:
4 years, 2 months ago by Clemens Hammacher Modified:
4 years, 2 months ago CC:
v8-reviews_googlegroups.com, devtools-reviews_chromium.org Target Ref:
refs/pending/heads/master Project:
v8 Visibility:
Public. |
Description[wasm] Add inspector test for stack traces
This ensures that the stack traces show up correctly in
DevTools. I will later extend it for source view.
R=kozyatinskiy@chromium.org, yangguo@chromium.org, titzer@chromium.org
BUG=chromium:613110
Committed: https://crrev.com/5b6e39135442f3bd3e19c91d8645533e4e9976ac
Cr-Commit-Position: refs/heads/master@{#40392}
Patch Set 1 #
Total comments: 2
Patch Set 2 : Address comments #Patch Set 3 : Add native load function for inspector-test #Patch Set 4 : Remove obsolete code #
Depends on Patchset: Messages
Total messages: 34 (23 generated)
The CQ bit was checked by clemensh@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
Description was changed from ========== [wasm] Add inspector test BUG=v8:4203 ========== to ========== [wasm] Add inspector test for stack traces This ensures that the stack traces shows up correctly in DevTools. I will later extend it for source view. R=kozyatinskiy@chromium.org, yangguo@chromium.org, titzer@chromium.org BUG=v8:4203 ==========
clemensh@chromium.org changed reviewers: + kozyatinskiy@chromium.org, titzer@chromium.org, yangguo@chromium.org
https://codereview.chromium.org/2420093002/diff/1/test/inspector/testcfg.py File test/inspector/testcfg.py (right): https://codereview.chromium.org/2420093002/diff/1/test/inspector/testcfg.py#n... test/inspector/testcfg.py:47: return flags + [ protocoltestfilename, testfilename ] Can we have a separate way of adding additional test files instead of piggybacking them on flags?
The CQ bit was checked by clemensh@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
https://codereview.chromium.org/2420093002/diff/1/test/inspector/testcfg.py File test/inspector/testcfg.py (right): https://codereview.chromium.org/2420093002/diff/1/test/inspector/testcfg.py#n... test/inspector/testcfg.py:47: return flags + [ protocoltestfilename, testfilename ] On 2016/10/17 09:08:13, Yang wrote: > Can we have a separate way of adding additional test files instead of > piggybacking them on flags? Yeah, probably a good idea. This way we can also fix the path separator for windows. Done.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by clemensh@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was checked by clemensh@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== [wasm] Add inspector test for stack traces This ensures that the stack traces shows up correctly in DevTools. I will later extend it for source view. R=kozyatinskiy@chromium.org, yangguo@chromium.org, titzer@chromium.org BUG=v8:4203 ========== to ========== [wasm] Add inspector test for stack traces This ensures that the stack traces show up correctly in DevTools. I will later extend it for source view. R=kozyatinskiy@chromium.org, yangguo@chromium.org, titzer@chromium.org BUG=v8:4203 ==========
On 2016/10/17 09:41:04, Clemens Hammacher wrote: > https://codereview.chromium.org/2420093002/diff/1/test/inspector/testcfg.py > File test/inspector/testcfg.py (right): > > https://codereview.chromium.org/2420093002/diff/1/test/inspector/testcfg.py#n... > test/inspector/testcfg.py:47: return flags + [ protocoltestfilename, > testfilename ] > On 2016/10/17 09:08:13, Yang wrote: > > Can we have a separate way of adding additional test files instead of > > piggybacking them on flags? > > Yeah, probably a good idea. This way we can also fix the path separator for > windows. > Done. I reworked the patch; it now adds a load() method for inspector tests, similar to the existing load method in the d8 shell (used in mjsunit tests).
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
lgtm
lgtm
The CQ bit was checked by clemensh@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: v8_presubmit on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_presubmit/builds/26655)
Description was changed from ========== [wasm] Add inspector test for stack traces This ensures that the stack traces show up correctly in DevTools. I will later extend it for source view. R=kozyatinskiy@chromium.org, yangguo@chromium.org, titzer@chromium.org BUG=v8:4203 ========== to ========== [wasm] Add inspector test for stack traces This ensures that the stack traces show up correctly in DevTools. I will later extend it for source view. R=kozyatinskiy@chromium.org, yangguo@chromium.org, titzer@chromium.org BUG=chromium:613110 ==========
The CQ bit was checked by clemensh@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== [wasm] Add inspector test for stack traces This ensures that the stack traces show up correctly in DevTools. I will later extend it for source view. R=kozyatinskiy@chromium.org, yangguo@chromium.org, titzer@chromium.org BUG=chromium:613110 ========== to ========== [wasm] Add inspector test for stack traces This ensures that the stack traces show up correctly in DevTools. I will later extend it for source view. R=kozyatinskiy@chromium.org, yangguo@chromium.org, titzer@chromium.org BUG=chromium:613110 ==========
Message was sent while issue was closed.
Committed patchset #4 (id:60001)
Message was sent while issue was closed.
Description was changed from ========== [wasm] Add inspector test for stack traces This ensures that the stack traces show up correctly in DevTools. I will later extend it for source view. R=kozyatinskiy@chromium.org, yangguo@chromium.org, titzer@chromium.org BUG=chromium:613110 ========== to ========== [wasm] Add inspector test for stack traces This ensures that the stack traces show up correctly in DevTools. I will later extend it for source view. R=kozyatinskiy@chromium.org, yangguo@chromium.org, titzer@chromium.org BUG=chromium:613110 Committed: https://crrev.com/5b6e39135442f3bd3e19c91d8645533e4e9976ac Cr-Commit-Position: refs/heads/master@{#40392} ==========
Message was sent while issue was closed.
Patchset 4 (id:??) landed as https://crrev.com/5b6e39135442f3bd3e19c91d8645533e4e9976ac Cr-Commit-Position: refs/heads/master@{#40392} |