Cron CI is failing
IAlibay opened this issue · comments
Looks like Cron CI is has been failing for at least two iterations. From the look of things it's two separate things: one was a setup-python call, the other some miniconda install. In both cases it's setting up Python.
This might be part of the issue:
API rate limit exceeded for 20.97.191.242. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)
Is it possible that we're just attempting to do too many gh API calls in the one runner? Could the runner be further split up?
Sees to have ran fine in the last run - may have been a temporary upstream issue.