-
Notifications
You must be signed in to change notification settings - Fork 135
cargo test --all-features
fails during test_compile_fail
with PermissionDenied
when crate directory is read-only
#421
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
Comments
@dkg I think we won't be able to overcome this limitation as the whole thing is handled by the Either allow writing to temporary directories on CI, or if that is not possible, use |
@tyranron thanks for the review. If the problem is with in the debian CI, there are definitely writable temporary directories available, but they are not within the source tree. |
@dkg as far as I see, |
From a quick look, this is definitely a bug in That said, while testing locally, I wasn't able to get the tests to pass on 1.75, 1.81, 1.82 or 1.83. @dkg speaking from experience, while Cargo itself does allow for out-of-source builds, a lot of the ecosystem just doesn't test for it and it's often broken. Edit: dtolnay/trybuild#298 |
dtolnay replied, and it is a limitation of Cargo: rust-lang/cargo#9661 To get around it, you need to set |
@jaskij thanks for looking into it! |
Uh oh!
There was an error while loading. Please reload this page.
In Debian, the continuous integration service by default tests each crate from a read-only copy of the published crate (not from git).
When testing a read-only tree of
derive_more
1.0.0, it fails with a bunch ofPermissionDenied
errors duringtest_compile_fail
. I think these tests are trying to write a copy of stderr to disk somewhere in tree.There are a few other errors/warnings mixed in there, but i think the predominant issue is the read-only filesystem:
In the debian CI, the
--all-features
test is known asrust-derive-more:@
.output from the test logs:
The text was updated successfully, but these errors were encountered: