-
Notifications
You must be signed in to change notification settings - Fork 81
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 "Cannot decode JSON from PhantomJS runner" for phantomjs v1.9.8 #176
Comments
Hi @fifigyuri Thanks for the report. Can you please enable debug support for GuardJasmine and report what it shows it receives? You can enable debugging by changing the Guardfile from something like:
To:
|
Thank you for you help. Here it is:
|
Interesting. That looks like phantomjs is outputting an error message that is interfering with the JSON output. I wonder what's triggering the "Unsafe JavaScript attempt to access frame with URL about:blank"? The message seems to indicate that it comes from guard-jasmine itself, but I'm not sure why you are receiving the message but others are not. Two questions:
|
Appears to be introduced in PhantomJS v1.9.8 and fixed in ariya/phantomjs#12720 |
I've just cut a new 2.0.1 release that incorporates the fix from #177. Please give it a try and see if that fixes the issue. |
thank you, I tried to start it by
|
@fifigyuri - that should be fixed by this PR: #181 You can test it by putting this in your Gemfile: gem 'guard-jasmine', github: 'guard/guard-jasmine', branch: 'update_guard_compat' |
@fifigyuri I've just merged #181 and am testing it now. Assuming that goes well, I'll push out a 2.0.2 release shortly that should resolve this. |
ok, i've tested out #181 and appears to work excellently on my system. I've also added some improved error reporting and have cut a 2.0.2 release. Please give that a try and let me know how it works. |
After bundle update, rails 4.2 , phamtom 1.9.8 I am getting the following error Small note |
Hi sahin, I doubt that the error you are receiving is related. Would it be possible for you to share your Guardfile? |
|
@sahin - could you rerun guard with the '-d' option? (your Guardfile seems fine) Does Are there any errors in your |
The issue I reported is fixed for me.. no |
@shahin: I looked over the Guardfile, it looks correct. I then attempted to locate the "An error occurred in the Jasmine runner" message in the code base and it's only used when the "guard-jasmine" command line is used. If that's the case, then the Guardfile doesn't come into play at all. I've just pushed up a tiny code change to include more details about the error that's occurring. If you could, please change your Gemfile to include Guard Jasmine from the latest git source. The line should look like: gem 'guard-jasmine', github: 'guard/guard-jasmine' After doing so, run I'm pretty sure you'll still receive an error, but it will hopefully provide enough details now so we can figure out if it's occurring inside guard-jasmine or perhaps in your spec's code. I'm going to close this issue for right now since it's not related to the error you're receiving. Please open a new issue with the contents of the updated error message and we'll figure it out. |
I updated the gem with guard-jasmine. now when I run I am getting. Guard::Jasmine starts Jasmine Gem test server on port 57881. |
when I run like this ruby -S rake jasmine JASMINE_PORT=8888 RAILS_ENV=test I can see the jasmine test page with no problem. |
This should fix the incompatibility with Travis' phantomjs. The build was failing with the message: "Cannot decode JSON from PhantomJS runner", which according to guard/guard-jasmine#176 has been fixed.
Running the specs in the browser pass, but running guard-jasmine fails with "Cannot decode JSON from PhantomJS runner".
The text was updated successfully, but these errors were encountered: