Skip to content

rustdoc: a lot of test causes OS Error 8 on Win32 #16690

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

Closed
klutzy opened this issue Aug 23, 2014 · 3 comments
Closed

rustdoc: a lot of test causes OS Error 8 on Win32 #16690

klutzy opened this issue Aug 23, 2014 · 3 comments
Labels
T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Comments

@klutzy
Copy link
Contributor

klutzy commented Aug 23, 2014

for i in range(200):
    print "/// ```"
    print "/// assert!(1u == 1u);"
    print "/// ```"
    print "fn dummy_" + str(i) + "() {}"
$ python gen.py > lib.rs
$ rustdoc.exe --test lib.rs
<snip>

failures:

---- dummy_79_0 stdout ----
        error: could not exec the linker `gcc`: OS Error 8: <os-specific message>

        error: aborting due to previous error
        task 'dummy_79_0' failed at 'Box<Any>', C:\home\stone\rust\src\libsyntax\ast_util.rs:776

<snip>

test result: FAILED. 173 passed; 27 failed; 0 ignored; 0 measured

(The number of failures vary)

I met this during check-stage2-T-i686-pc-mingw32-H-i686-pc-mingw32-doc-crate-std.

@huonw
Copy link
Member

huonw commented Aug 23, 2014

This is possibly due to spawning too many rustc processes (I assume it's currently spawning one for each code block all at the same time?).

@alexcrichton
Copy link
Member

It looks like error 8 is OOM, is there anything we can really do about that? Does your system have an adequate amount of memory to run all these tests in parallel?

@klutzy
Copy link
Contributor Author

klutzy commented Aug 25, 2014

I've checked there was sufficient memory and the failure occurred even if RUST_TEST_TASKS=1 is given.
Well, however I'm failing to reproduce the error now.. so let's close this until real reason is found ¯_(ツ)_/¯

@klutzy klutzy closed this as completed Aug 25, 2014
matthiaskrgr pushed a commit to matthiaskrgr/rust that referenced this issue Mar 10, 2024
fix: use 4 spaces for indentation in macro expansion

Partial fix for rust-lang#16471.

In the previous code, the indentation produced by macro expansion was set to 2 spaces. This PR modifies it to 4 spaces for the sake of consistency.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

3 participants