-
Notifications
You must be signed in to change notification settings - Fork 56
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
Could not connect to UI error in Jenkins #42
Comments
I'm experiencing a similar problem. I think the "UI" part in the message comes from the folder name "Angular UI Toolkit" in your path to the jenkins job. I'm having a similar issue when trying to run browserstack local, where my path also contain spaces. So I think there's some issue with handling paths which contain spaces. In my case, I'm getting: "Could not connect to Win7!" and Win7 is a part of the path where the script is executing. My logs (similar to yours):
|
I am having the same issue with Jenkins installed at Any solution for this yet? |
HI,
I am getting the below error in jenkins while executing e2e.
Connecting local error { Error
at F:\Jenkins\workspace\Angular UI Toolkit\node_modules\browserstack-local\lib\Local.js:57:20
at ChildProcess.exithandler (child_process.js:262:7)
at emitTwo (events.js:125:13)
at ChildProcess.emit (events.js:213:7)
at maybeClose (internal/child_process.js:897:16)
at Socket.stream.socket.on (internal/child_process.js:340:11)
at emitOne (events.js:115:13)
at Socket.emit (events.js:210:7)
at Pipe._handle.close [as _onclose] (net.js:548:12)
name: 'LocalError',
message: 'Could not connect to UI!',
extra: undefined }
F:\Jenkins\workspace\Angular UI Toolkit\node_modules\protractor\node_modules\q\q.js:155
throw e;
^
Error
at F:\Jenkins\workspace\Angular UI Toolkit\node_modules\browserstack-local\lib\Local.js:57:20
at ChildProcess.exithandler (child_process.js:262:7)
at emitTwo (events.js:125:13)
at ChildProcess.emit (events.js:213:7)
at maybeClose (internal/child_process.js:897:16)
at Socket.stream.socket.on (internal/child_process.js:340:11)
at emitOne (events.js:115:13)
at Socket.emit (events.js:210:7)
at Pipe._handle.close [as _onclose] (net.js:548:12)
The text was updated successfully, but these errors were encountered: