Rejection Error on a Local site (similar to others with a debug attached) about grunt-phantomas HOT 18 CLOSED

Hey,

it fails constantly? And no run succeeds?

from grunt-phantomas.

Absolutely the same as the others... Phantomas times out.

from grunt-phantomas.

Related to #21.

from grunt-phantomas.

That's correct. I could not get it to succeed on that site no matter how many runs. Fortunately, the site is not important to me. If I reinstall a fresh Drupal 7 on the url, Phantomas works.

from grunt-phantomas.

You played with the timeout param already?
We're probably facing a phantomas bug. :)

from grunt-phantomas.

I did. I tried 60 seconds. It waited 60 seconds, but didn't change the results. It's a weird one because Phantomas appears to have run as I can see the output.

from grunt-phantomas.

Hmm, okay. Any live site you're facing that issue? Or really only local?

from grunt-phantomas.

It works on many of my local sites. It's really just this one site. I'm trying to figure out what's different about it. I'll let you know if I can replicate it on my production VPS. I need to remove some internal content from it first.

from grunt-phantomas.

Thanks for investigating.

from grunt-phantomas.

One question:

when you run phantomas --url http://yoursite.com/ do you get the status code 252?

Time spent on backend / frontend: 7% / 93%
FAIL: 252

from grunt-phantomas.

Yes I always get error 252 even if I encrese the timeout.—
Nicola Zanon

On Fri, Jan 17, 2014 at 9:54 PM, Stefan Judis [email protected]
wrote:

One question:
when you run phantomas --url http://yoursite.com/ do you get the status code 252?

Time spent on backend / frontend: 7% / 93%
FAIL: 252

---

Reply to this email directly or view it on GitHub:
#23 (comment)

from grunt-phantomas.

Okay, we got it. 😄

Let me dig into phantomas and check what's going on. I can not promise anything. ;)
Will open an issue afterwards.

Grunt-phantomas relies on the status code ( which is absolutely correct in my mind ). So unfortunately I can not do anything from my side.

from grunt-phantomas.

Please check version 0.4.0 and feel free to close if it's working now? 😄

from grunt-phantomas.

@Greg-Boggs I'm closing this issue, now. Feel free to reopen, if you still have any troubles. :)

from grunt-phantomas.

Hi, I have the same problem than @Greg-Boggs... I would like to test pages locally but I have "return_code: -201"...

from grunt-phantomas.

Hmm... 201 is a new one.
Do you mind filing another issues including config and version numbers? :)

from grunt-phantomas.

My mistake, snarl return me the -201... In fact, phantomas return me the 252 when a test my website on "http://localhost:4000". :-/

from grunt-phantomas.

Well, basically that's not a problem on the side of grunt-phantomas.

Do I understand you correct, that you already tried using phantomas without grunt-phantomas?
If not, could you please install phantomas ( npm install -g phantomas ) and then run it against your disired site ( phantomas --url http://yoursite.com --verbose) multiple times.

Please keep your eyes open for this:

Time spent on backend / frontend: 7% / 93%
FAIL: 252

I'd like to support, but when it's on the side of phantomas I'm out. ;)

from grunt-phantomas.