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

rake test:javascript should fail if the JS engine crashes #12765

Closed
himdel opened this issue Nov 21, 2016 · 4 comments
Closed

rake test:javascript should fail if the JS engine crashes #12765

himdel opened this issue Nov 21, 2016 · 4 comments
Assignees

Comments

@himdel
Copy link
Contributor

himdel commented Nov 21, 2016

Between #11762 and #12640, our JS tests would crash the phantomjs server (infinite loop leads to a Segmentation fault), but the test suite would still pass.

That's bad, if phantomjs crashes, the rake task should too.

$ git log -1 --oneline
638f4d7 Merge pull request #12424 from tinaafitz/notification_provisioned

$ rake test:javascript ; echo STATUS: $?
Puma starting in single mode...
* Version 3.3.0 (ruby 2.3.1-p112), codename: Jovial Platypus
* Min threads: 5, max threads: 5
* Environment: development
* Listening on tcp://0.0.0.0:40227
Use Ctrl-C to stop
jasmine server started
...............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................1   0x1b67967 /home/himdel/.phantomjs/2.1.1/x86_64-linux/bin/phantomjs() [0x1b67967]
2   0x1baac35 /home/himdel/.phantomjs/2.1.1/x86_64-linux/bin/phantomjs() [0x1baac35]
3   0x1b9369c /home/himdel/.phantomjs/2.1.1/x86_64-linux/bin/phantomjs() [0x1b9369c]
4   0x18970ad /home/himdel/.phantomjs/2.1.1/x86_64-linux/bin/phantomjs() [0x18970ad]
5   0x1896ace /home/himdel/.phantomjs/2.1.1/x86_64-linux/bin/phantomjs() [0x1896ace]
6   0x1896ddf /home/himdel/.phantomjs/2.1.1/x86_64-linux/bin/phantomjs() [0x1896ddf]
7   0x1907ec8 /home/himdel/.phantomjs/2.1.1/x86_64-linux/bin/phantomjs() [0x1907ec8]
8   0x7f0133d1d801 [0x7f0133d1d801]
PhantomJS has crashed. Please read the bug reporting guide at
<http://phantomjs.org/bug-reporting.html> and file a bug report.
Segmentation fault

703 specs, 0 failures
STATUS: 0
@blomquisg blomquisg added the ui label Jan 12, 2017
@dclarizio
Copy link

@miq-bot assign @himdel

@miq-bot
Copy link
Member

miq-bot commented Sep 30, 2017

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!

@miq-bot miq-bot added the stale label Sep 30, 2017
@himdel
Copy link
Contributor Author

himdel commented Oct 3, 2017

@miq-bot move_issue ManageIQ/manageiq-ui-classic

@miq-bot
Copy link
Member

miq-bot commented Oct 3, 2017

This issue has been moved to ManageIQ/manageiq-ui-classic#2278

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

No branches or pull requests

4 participants