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

Spurious failure "failed to remove file ... Access is denied" in cargo test profile_selection_check_all_targets* on Windows #56040

Closed
kennytm opened this issue Nov 18, 2018 · 3 comments
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@kennytm
Copy link
Member

kennytm commented Nov 18, 2018

Symptom: On x86_64-msvc-cargo, a cargo test with name like profile_selection_check_all_targets* failed to build due to error like

error: failed to remove file `C:\projects\rust\build\x86_64-pc-windows-msvc\stage2-tools\x86_64-pc-windows-msvc\cit\t988\foo\target\debug\libfoo.rmeta`
Caused by:
  Access is denied. (os error 5)

Previous instances:

Note: the cargo submodule was most recently updated by #55830 on 2018-11-10T15:03:11Z, but the 7 days of inactivity suggests #55830 may not be the cause.

@kennytm kennytm added A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. labels Nov 18, 2018
@ehuss
Copy link
Contributor

ehuss commented Nov 18, 2018

I think this will be fixed once #55999 lands. There is a change in how .rmeta files are handled (rust-lang/cargo#6292) that looks like it will clear it up.

I don't know why it is showing up all of a sudden. I was going to say it may be related to the switch to gce, but it also happened on cargo's ci (rust-lang/cargo#6319).

@kennytm
Copy link
Member Author

kennytm commented Nov 18, 2018

Thanks. Raised the priority of #55999.

@ehuss
Copy link
Contributor

ehuss commented Jun 24, 2022

Closing as this was resolved a long time ago.

@ehuss ehuss closed this as completed Jun 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

2 participants