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.

Sign up for GitHub

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

Jump to bottom

Failed to clone the index on CI #73992

Closed
pietroalbini opened this issue Jul 3, 2020 · 3 comments
Closed

Failed to clone the index on CI #73992

pietroalbini opened this issue Jul 3, 2020 · 3 comments
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@pietroalbini
Copy link
Member

We started seeing a lot of failures cloning the crates.io index across the rustc CI.
@pietroalbini pietroalbini added A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Jul 3, 2020
This was referenced Jul 3, 2020
Merged
Merged
@RalfJung
Copy link
Member

RalfJung commented Jul 3, 2020

More failures:

@JohnTitor JohnTitor mentioned this issue Jul 5, 2020
Merged
@oliviacrain oliviacrain mentioned this issue Oct 24, 2020
Merged
@oliviacrain
Copy link
Contributor

Looks like this is still happening as of Oct 19 - #76688 has the same failure to clone the crates.io index on an 1686 platform.

Logs link for that run

This is a bit of a weird one- it seems like this issue is happening despite bootstrapping using the cargo beta from 2020-10-16, which includes the fix for this issue (rust-lang/cargo#8517).

@Enselic
Copy link
Member

Enselic commented Dec 16, 2023

Triage: If this was still a problem I think this issue would not have gone silent? Closing as obsolete.

@Enselic Enselic closed this as not planned Won't fix, can't repro, duplicate, stale Dec 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Enselic @RalfJung @pietroalbini @oliviacrain