You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I keep getting build error because installing Jim's covr package fails. It appears that the github api refuses to serv travis-ci requests.
In .travis.yml:
r_github_packages:
- jimhester/covr
Here's the error I get:
The command "Rscript -e 'devtools::install_github(c("jimhester/covr"), build_vignettes = FALSE)'" failed and exited with 1 during
I added curl -i to the .travis.yml to see what's going on, and I get
$ curl -i https://api.github.com/repos/jimhester/covr/zipball/master
HTTP/1.1 403 Forbidden
Server: GitHub.com
Date: Mon, 29 Feb 2016 12:56:17 GMT
[snip]
{
"message": "API rate limit exceeded for 52.0.240.122. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
"documentation_url": "https://developer.github.com/v3/#rate-limiting"
}
I'm out of wits except setting up somehow oAuth from travis, which I'd rather avoid.
As an aside, I used to do this with a derivative of a script of Dirk E., based on the language c directive and strangely enough that never showed this problem.
Yes this is a known transient issue because GitHub's rate limiting is per IP address, so Travis can exceed them. You can wait a few minutes and re-run your build.
@craigcitro, @hadley, @jimhester
I keep getting build error because installing Jim's covr package fails. It appears that the github api refuses to serv travis-ci requests.
In
.travis.yml
:Here's the error I get:
I added
curl -i
to the.travis.yml
to see what's going on, and I getI'm out of wits except setting up somehow oAuth from travis, which I'd rather avoid.
As an aside, I used to do this with a derivative of a script of Dirk E., based on the
language c
directive and strangely enough that never showed this problem.Some links: travis-ci log | github repo | travis config
The text was updated successfully, but these errors were encountered: