Skip to content
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

CI: Failed to clone package repo #301

Closed
TylerLoewen opened this issue Jul 20, 2021 · 3 comments
Closed

CI: Failed to clone package repo #301

TylerLoewen opened this issue Jul 20, 2021 · 3 comments
Labels

Comments

@TylerLoewen
Copy link

https://github.com/invenia/PkgTemplates.jl/runs/3100066407?check_suite_focus=true

##[debug]/bin/bash --noprofile --norc -e -o pipefail /Users/runner/work/_temp/d39967ca-a251-47c0-98b0-c27b77f7fb26.sh
    Updating registry at `~/.julia/registries/General`
    Updating git-repo `https://github.com/JuliaRegistries/General.git`
┌ Warning: Some registries failed to update:
│     — /Users/runner/.julia/registries/General — failed to fetch from repo
└ @ Pkg.Types /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.6/Pkg/src/Types.jl:1246
     Cloning [78c3b35d-d492-501b-9361-3d52fe80e533] Mocking from https://github.com/invenia/Mocking.jl.git
ERROR: failed to clone from https://github.com/invenia/Mocking.jl.git, error: GitError(Code:ERROR, Class:Net, failed to resolve address for github.com: nodename nor servname provided, or not known)
@TylerLoewen TylerLoewen changed the title Failed to clone package repo CI: Failed to clone package repo Jul 20, 2021
@christopher-dG
Copy link
Member

This looks to me like a random network failure on the hosted runner, especially since it only happened on one job rather than all of them

@TylerLoewen
Copy link
Author

That makes sense to me. I created this issue to document the occurrence but since it's a one-off issue and there isn't any way to resolve it it may be best to close the issue?

@christopher-dG
Copy link
Member

Yeah, this is GH's fault and isn't specific to this repo either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants