-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Cargo doc broken on nightly-2017-09-11 #44487
Labels
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
Milestone
Comments
alexcrichton
added
the
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
label
Sep 11, 2017
Looks like this is because |
Likely caused by #44260 |
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Sep 11, 2017
Apparently `File::create` was called when there was an existing hard link or the like, causing an existing file to get accidentally truncated! Closes rust-lang#44487
bors
added a commit
that referenced
this issue
Sep 11, 2017
rustbuild: Fix a distribution bug with rustdoc Apparently `File::create` was called when there was an existing hard link or the like, causing an existing file to get accidentally truncated! Closes #44487
On Appveyor I was getting a much more frustrating error:
Upon updating to the latest nightly locally I got a more helpful error:
|
Oh that's why my builds were failing attempting to commit an empty folder full of 'docs'... |
This was referenced Sep 12, 2017
Thank you guys! That fixed it :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
Cargo doc runs on nightly-2017-09-11 without displaying any errors or warnings, yet, it doesn't produce any outputs.
I am on nightly-unknown-linux-gnu on Linux Mint.
I tried with different nightly toolchains to see if it was a problem of my code, or if it was a problem of the toolchain.
I also tried on different machines and the result is the same.
I tried:
but I cannot find any pointer to the problem.
Example output when running cargo doc --open
The browser window doesn't open, the target/doc folder is empty and the usual xdg-open command is missing.
Does anybody else have the same problem?
The text was updated successfully, but these errors were encountered: