-
Notifications
You must be signed in to change notification settings - Fork 104
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
Everything is sad if bitbucket is down #70
Comments
I ran into the same issue today. In my case, it looks like BitBucket is not down, but rather they are returning 'Rate limit for this resource has been exceeded'. |
Same here, on a ci server, very annoying... |
Just as an update, as a workaround in CI, I ended up hosting my own version of the binary in S3, and am downloading that ahead of time so this gem sees that it already exists in my PATH. |
Thanks for sharing your workaround! |
Looks like the phantomjs team is working to setup alternative download locations: ariya/phantomjs#13953 |
I am getting this error VERY often on Circle CI |
Same here. I am using Semaphore. |
This works around an issue in Travis CI when attempting to install the PhantomJS dependency from the configured CDN. We don't depend on any particular behaviour from later PhantomJS releases, so this won't affect us. Reference: colszowka/phantomjs-gem#70
This works around an issue in Travis CI when attempting to install the PhantomJS dependency from the configured CDN. We don't depend on any particular behaviour from later PhantomJS releases, so this won't affect us. Reference: colszowka/phantomjs-gem#70
We're having this same issue on phantomjs 2.1.1.0 at the moment: |
One workaround is to use your CI environment's caching ability: This appears to improve our case. Also, Ubuntu 14.04 on CircleCI happens to include PhantomJS 2.1.1, avoiding any download until the next version is released. |
One suggestion would be to add the On the downside, the failed Let me know if you want a PR.
|
https://status.bitbucket.org/incidents/z029156p1svh
I don't mind the bad errors, I guess I wish my CI service cache proxied bitbucket for our builds. Not like phantomjs-2.1.1 has changed recently... |
Bitbucket is currently down, which causes the following.
One solution is to rescue and not re-raise this error if there is already a matching version of phantomjs in the PATH.
The text was updated successfully, but these errors were encountered: