debug doesnt work on 0.20.0

[alexwibowo]

Hi,

I have just tried the new 0.20.0 release, which i thought should have this fix: 2ca6541

But when I tried running protractor with debug option (protractor debug ), I got the following error:

E:\dev\modules\docViewerPortal\docViewerPortal-endToEndTest>protractor debug src/test/js/protractor.conf.js

node.js:723
throw new Error('Unknown signal: ' + sig);
^
Error: Unknown signal: SIGUSR1
at process.kill (node.js:723:17)
at new Runner (C:\Users\s74627\AppData\Roaming\npm\node_modules\protractor\lib\runner.js:26:13)
at process. (C:\Users\s74627\AppData\Roaming\npm\node_modules\protractor\lib\runFromL
auncher.js:31:20)
at process.EventEmitter.emit (events.js:98:17)
at handleMessage (child_process.js:318:10)
at Pipe.channel.onread (child_process.js:345:11)
[launcher] Runner Process Exited With Error Code: 8

Not sure if other people got it. For now I'm rolling back again to 0.18.1, where debug works. Oh, and I ran it on windows (command line) machine.

[juliemr]

Dang, is this a windows thing?

[juliemr]

Yes it is :(
node-inspector/node-inspector#212

[juliemr]

And we should be fixed in 0.20.1. Can someone with an actual windows machine confirm?

[alexwibowo]

Hi Julie. Brilliant. I can confirm it works on my windows machine now (with 0.20.1). Thanks a lot!

[juliemr]

Thanks for verifying, @alexwibowo !

[dineshdh]

Hi @juliemr.

I am still having trouble with browser.debugger() on Windows. Please see my comment in issue #552. Essentially my browser.debugger() does not pause the test so I can do some browser debugging.

Hope you can shed some light on this issue.

[juliemr]

Commented in #552

[mdudek]

Unfortunately, I must confirm that debugging is still broken in WebStorm(7/8) with Protractor 0.20.1. ;-(