You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 of PermissionDenied errors during test_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:
@dkg I think we won't be able to overcome this limitation as the whole thing is handled by the trybuild crate and there is no configuration for this behavior.
Either allow writing to temporary directories on CI, or if that is not possible, use -- --skip compile_fail in the end of your cargo test commands to omit them.
@tyranron thanks for the review. If the problem is with trybuild, have you reported any issue to that crate, that it will fail when the source tree is unwritable?
in the debian CI, there are definitely writable temporary directories available, but they are not within the source tree.
From a quick look, this is definitely a bug in trybuild - seems like it fails to pass the value of --target-dir somewhere along the way.
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.
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: