tests/run-make/rustdoc-io-error/rmake.rs


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

// This test verifies that rustdoc doesn't ICE when it encounters an IO error
// while generating files. Ideally this would be a rustdoc-ui test, so we could
// verify the error message as well.
//
// It operates by creating a temporary directory and modifying its
// permissions so that it is not writable. We have to take special care to set
// the permissions back to normal so that it's able to be deleted later.

//@ ignore-riscv64
//@ ignore-arm
// FIXME: The riscv64gc-gnu and armhf-gnu build containers run as root,
// and can always write into `inaccessible/tmp`. Ideally, these docker
// containers would use a non-root user, but this leads to issues with
// `mkfs.ext4 -d`, as well as mounting a loop device for the rootfs.
//@ ignore-windows - the `set_readonly` functions doesn't work on folders.

use run_make_support::{path, rfs, rustdoc};

fn main() {
    let out_dir = path("rustdoc-io-error");
    rfs::create_dir(&out_dir);
    let mut permissions = rfs::metadata(&out_dir).permissions();
    let original_permissions = permissions.clone();

    permissions.set_readonly(true);
    rfs::set_permissions(&out_dir, permissions);

    let output = rustdoc().input("foo.rs").out_dir(&out_dir).env("RUST_BACKTRACE", "1").run_fail();

    rfs::set_permissions(&out_dir, original_permissions);

    output
        .assert_exit_code(1)
        .assert_stderr_contains("error: couldn't generate documentation: Permission denied");
}