Test runner fails if /tmp is mounted with "noexec" #12558
Comments
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Apr 4, 2024
[`let_and_return`]: avoid linting when code between last stmt and return expr is cfg'd out Fixes rust-lang#9150 This moves `span_contains_cfg` to utils and starts using it in `let_and_return` as well. changelog: [`let_and_return`]: avoid linting when code between the last statement and the final return expression is `#[cfg]`ed out
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running
make check, it failed during thedoc-stdtarget with 244 failures and 0 successes. All of them produced an error of the form "'couldn't run the test: permission denied', [snip]/rust/src/librustdoc/test.rs:131".Investigating this further, it turns out to be because rustdoc's
test.rsattempts to create a file in a temporary directory and then execute it. By default on my platform, this happens in/tmp. My/tmp, however, is mounted with the "noexec" option that prevents executing files from it.Arguably this is just user error on my part for configuring things this way, but I don't think it's an uncommon setup. It was also quite a mysterious way for things to fail. Perhaps the test runner could check for this and fail more usefully?
In the meantime, a workaround is to run the tests with the environment variable
TMPDIRset to something else.The text was updated successfully, but these errors were encountered: