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

Question: Any idea why electron update in 2.1.4 broke Jenkins? #525

Closed
antpaw opened this issue Mar 2, 2016 · 10 comments
Closed

Question: Any idea why electron update in 2.1.4 broke Jenkins? #525

antpaw opened this issue Mar 2, 2016 · 10 comments

Comments

@antpaw
Copy link
Contributor

antpaw commented Mar 2, 2016

This is just a question and not really an issue:
Have you experienced any troubles with CI integration, (I believe your using circleci) after updating to 2.1.4?

Thanks

@rosshinkley
Copy link
Contributor

@antpaw Yeah, there are intermittent failures I haven't gotten to the bottom of. Have you had any luck?

@antpaw
Copy link
Contributor Author

antpaw commented Apr 3, 2016

no I still have no idea, we are using jenkins and installed bunch of plugins to get electron working, and it still is, but with the newst version it just "hangs" without any errors or logs. no idea how to debug it.

@rosshinkley
Copy link
Contributor

rosshinkley commented May 24, 2016

@antpaw Have you given this a try with later versions? I wonder if you're hitting the Xvfb hang from #561.

@antpaw
Copy link
Contributor Author

antpaw commented May 31, 2016

@rosshinkley hey, i've just checked the 2.5.0 version, it still hangs without any logs. the highest version it works for me is 2.1.3

@rosshinkley
Copy link
Contributor

@antpaw Do you have DEBUG output? What version of Node are you running?

@antpaw
Copy link
Contributor Author

antpaw commented May 31, 2016

node version 4.2.6

just turned debugging on and saw this:

+ DEBUG=nightmare* NODE_ENV=testing-production make ftest
node_modules/.bin/mocha --harmony test/functional/ ./apps/**/test/functional/*.coffee --opts test/functional/mocha.opts --reporter dot
Listening on port 4600
Tue, 31 May 2016 14:25:51 GMT nightmare running
Tue, 31 May 2016 14:25:51 GMT nightmare electron child process exited with code 127: command not found - you may not have electron installed correctly

"...may not have electron installed correctly" but it doesn't exit the process

@rosshinkley
Copy link
Contributor

Can you run it again with DEBUG=*,-mocha* under 2.5.0? Also, what operating system/version are you running?

@antpaw
Copy link
Contributor Author

antpaw commented May 31, 2016

ah, thanks now its possible to see much more. I assume it fails every test very slowly or tries to recover over and over again.

Listening on port 4600
Tue, 31 May 2016 18:03:24 GMT nightmare running
Tue, 31 May 2016 18:03:24 GMT electron:stderr /var/lib/jenkins/workspace/webapp-staging/node_modules/electron-prebuilt/dist/electron: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory
Tue, 31 May 2016 18:03:24 GMT nightmare electron child process exited with code 127: command not found - you may not have electron installed correctly
  ․Tue, 31 May 2016 18:03:54 GMT nightmare running
․Tue, 31 May 2016 18:04:24 GMT nightmare running
Tue, 31 May 2016 18:04:24 GMT electron:stderr /var/lib/jenkins/workspace/webapp-staging/node_modules/electron-prebuilt/dist/electron: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory
Tue, 31 May 2016 18:04:24 GMT nightmare electron child process exited with code 127: command not found - you may not have electron installed correctly
․Tue, 31 May 2016 18:04:54 GMT nightmare running
․Tue, 31 May 2016 18:05:25 GMT nightmare running
Tue, 31 May 2016 18:05:25 GMT electron:stderr /var/lib/jenkins/workspace/webapp-staging/node_modules/electron-prebuilt/dist/electron: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory
Tue, 31 May 2016 18:05:25 GMT nightmare electron child process exited with code 127: command not found - you may not have electron installed correctly
․Tue, 31 May 2016 18:05:55 GMT nightmare running
․Tue, 31 May 2016 18:06:25 GMT nightmare running
Tue, 31 May 2016 18:06:25 GMT electron:stderr /var/lib/jenkins/workspace/webapp-staging/node_modules/electron-prebuilt/dist/electron: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory
Tue, 31 May 2016 18:06:25 GMT nightmare electron child process exited with code 127: command not found - you may not have electron installed correctly
․Tue, 31 May 2016 18:06:55 GMT nightmare running
․Tue, 31 May 2016 18:07:25 GMT nightmare running
Tue, 31 May 2016 18:07:25 GMT electron:stderr /var/lib/jenkins/workspace/webapp-staging/node_modules/electron-prebuilt/dist/electron: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory
Tue, 31 May 2016 18:07:25 GMT nightmare electron child process exited with code 127: command not found - you may not have electron installed correctly
․Tue, 31 May 2016 18:07:55 GMT nightmare running
․Tue, 31 May 2016 18:08:25 GMT nightmare running
Tue, 31 May 2016 18:08:25 GMT electron:stderr /var/lib/jenkins/workspace/webapp-staging/node_modules/electron-prebuilt/dist/electron: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory
Tue, 31 May 2016 18:08:25 GMT nightmare electron child process exited with code 127: command not found - you may not have electron installed correctly

@rosshinkley
Copy link
Contributor

I just hit this when working on the Circle tests to include multiple NodeJS versions. I had a sneaking suspicion you were missing libnotify. If you're on Ubuntu, installing libnotify-bin with apt-get should solve it for you.

@antpaw
Copy link
Contributor Author

antpaw commented May 31, 2016

That's what I though when I opened this issue! Thanks so much, I will try it tomorrow (gmt)

@antpaw antpaw closed this as completed Jun 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants