Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Process blocked for too long #119

Closed
dhowe opened this issue Apr 4, 2015 · 1 comment
Closed

Error: Process blocked for too long #119

dhowe opened this issue Apr 4, 2015 · 1 comment
Labels

Comments

@dhowe
Copy link

dhowe commented Apr 4, 2015

I get the following errors when I run a group of test via node-qunit:

[20:50:10] Error: Command failed: /bin/sh -c ./node_modules/.bin/qunit -l "{ globalSummary: true, errors: true }" -c src/mylib.js -d src/mylib_lts.js src/mylib_dict.js -t "test/mylib-qunit-helpers.js" ./test/mylib-tests1.js ./test/mylib-tests2.js ./test/mylib-tests3.js
[Error: Process blocked for too long]

    at ChildProcess.exithandler (child_process.js:744:12)
    at ChildProcess.emit (events.js:110:17)
    at maybeClose (child_process.js:1008:16)
    at Socket.<anonymous> (child_process.js:1176:11)
    at Socket.emit (events.js:107:17)
    at Pipe.close (net.js:476:12)

I see it referenced here, but I'm not sure of the status... Any info or a workaround would be great, as my tests now fail when I try to run them in node (though they are ok in phantomjs)

@kof
Copy link
Contributor

kof commented Apr 5, 2015

See maxBlockDuration option if its normal for your task to block the process for seconds - increase it.

@kof kof closed this as completed Apr 5, 2015
@kof kof added the support label Apr 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 participants