Skip to content
This repository has been archived by the owner on Jun 19, 2019. It is now read-only.

test-debugger-remote asserts: child should not exit normally #345

Open
mykmelez opened this issue Dec 15, 2016 · 1 comment
Open

test-debugger-remote asserts: child should not exit normally #345

mykmelez opened this issue Dec 15, 2016 · 1 comment

Comments

@mykmelez
Copy link
Contributor

=== release test-debugger-remote ===
Path: debugger/test-debugger-remote
connecting to localhost:5959 ... ok
/Users/myk/Projects/spidernode/out/Release/node --debug-brk=5959 /Users/myk/Projects/spidernode/test/fixtures/empty.js
/Users/myk/Projects/spidernode/out/Release/node debug localhost:5959
Assertion failure: !joinable(), at /Users/myk/Projects/spidernode/deps/spidershim/spidermonkey/js/src/threading/Thread.h:122
Command: out/Release/node /Users/myk/Projects/spidernode/test/debugger/test-debugger-remote.js
--- TIMEOUT ---

@mykmelez mykmelez added this to the pass Node tests milestone Dec 15, 2016
@mykmelez mykmelez changed the title test-debugger-remote times out test-debugger-remote asserts: child should not exit normally Apr 7, 2017
@mykmelez
Copy link
Contributor Author

mykmelez commented Apr 7, 2017

Now instead of timing out it asserts child should not exit normally:

=== release test-debugger-remote ===
Path: debugger/test-debugger-remote
:0

AssertionError: child should not exit normally
Command: out/Release/node /Users/myk/Projects/spidernode/test/debugger/test-debugger-remote.js

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant