This repository has been archived by the owner on Oct 15, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 340
Investigate new inspector test failure #292
Comments
kfarnung
added a commit
to kfarnung/node-chakracore
that referenced
this issue
Jun 12, 2017
Issues are tracked by nodejs#292
kfarnung
added a commit
to kfarnung/node-chakracore
that referenced
this issue
Jun 12, 2017
Issues are tracked by nodejs#292
kfarnung
added a commit
to kfarnung/node-chakracore
that referenced
this issue
Jun 12, 2017
* async-hooks/test-callback-error - depends on V8 option --abort-on-uncaught-exception * inspector/test-off-with-session-then-on - tracked by nodejs#292
kfarnung
added a commit
to kfarnung/node-chakracore
that referenced
this issue
Jun 12, 2017
* async-hooks/test-callback-error - depends on V8 option --abort-on-uncaught-exception * inspector/test-off-with-session-then-on - tracked by nodejs#292 PR-URL: nodejs#295
kfarnung
added a commit
to kfarnung/node-chakracore
that referenced
this issue
Jun 16, 2017
* Updated `inspector/test-inspector-exception` which required ChakraCore-specific logic and removed the flaky status * Marked `inspector/test-off-with-session-then-on` flaky; failure tracked by nodejs#292 Fixes nodejs#306 PR-URL: nodejs#307 Reviewed-By: Kunal Pathak <kunal.pathak@microsoft.com>
I don't know if this is related but I have been stuck with both VS Code and Chrome debuggers due to this: nodejs/node#7593 |
We'll track this work in #367. It looks like the |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After the latest merge there's a new failure in
test-inspector-break-when-eval
:When merging v8.1.0 there was also a new failure in
test-off-with-session-then-on
:The text was updated successfully, but these errors were encountered: