Skip to content

Intermittent ctrl_c_kills_everyone Windows test failure #41511

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
frewsxcv opened this issue Apr 24, 2017 · 2 comments
Closed

Intermittent ctrl_c_kills_everyone Windows test failure #41511

frewsxcv opened this issue Apr 24, 2017 · 2 comments
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason)

Comments

@frewsxcv
Copy link
Member

#41503 (comment)

running 1 test
test ctrl_c_kills_everyone ... FAILED
failures:
---- ctrl_c_kills_everyone stdout ----
	attempt 0: The directory is not empty. (os error 145)
attempt 1: Access is denied. (os error 5)
attempt 2: Access is denied. (os error 5)
attempt 3: Access is denied. (os error 5)
attempt 4: Access is denied. (os error 5)
attempt 5: Access is denied. (os error 5)
attempt 6: Access is denied. (os error 5)
attempt 7: Access is denied. (os error 5)
attempt 8: Access is denied. (os error 5)
attempt 9: Access is denied. (os error 5)
thread 'ctrl_c_kills_everyone' panicked at 'couldn't remove build directory after a few tries, seems like we won't be able to!', tests\death.rs:120
note: Run with `RUST_BACKTRACE=1` for a backtrace.
failures:
    ctrl_c_kills_everyone
test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured
error: test failed
thread 'main' panicked at 'tests failed for https://github.com/rust-lang/cargo', src\tools\cargotest\main.rs:98
note: Run with `RUST_BACKTRACE=1` for a backtrace.
command did not execute successfully: "C:\\projects\\rust\\build\\x86_64-pc-windows-msvc\\stage0-tools\\x86_64-pc-windows-msvc\\release\\cargotest.exe" "C:\\projects\\rust\\build\\x86_64-pc-windows-msvc\\stage0/bin\\cargo.exe" "C:\\projects\\rust\\build\\ct"
expected success, got: exit code: 101
Build completed unsuccessfully in 0:18:23
make: *** [Makefile:56: check-aux] Error 1
Command exited with code 2
@frewsxcv frewsxcv added the A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) label Apr 24, 2017
@alexcrichton
Copy link
Member

The test in question is in Cargo and tests whether ctrl-c actually kills Cargo's process tree.

I ... don't know how this'd happen. This means that for a full second something was alive which kept open a file in that build tree ...

@Mark-Simulacrum
Copy link
Member

This hasn't happened since then judging by GitHub not having any more than that one PR, so I'm going to close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason)
Projects
None yet
Development

No branches or pull requests

3 participants