-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Inconsistent doc output between normal build and --release flag #19290
Comments
Gan you give an example of the differences? I tried to reproduce this locally. |
Yea sure, look at this complete doc. When compiling with
I tried it several times locally just to be sure. The doc built by Travis wasn't showing the correct thing either. I added the Although I can't reproduce it with my current code anymore. |
Digging deeper into it... /master historycommit - Getting Travis to call cargo build --release - 4 hours ago /gh-pages historyTravis build 35 pushed to gh-pages - 4 hours ago Travis history35 - Getting Travis to call cargo build --release - (3 min 15 sec) about 4 hours ago Commit 33 and 34 were pushed at the same time, Travis apparently runs once per commit not per push. Travis overwrote itself online. because commit 33 finished before commit 34. TL;DR; it looks like it wasn't a rustdoc issue, I'm closing this up. |
Oh wow, that is confusing! Thanks for investigating this @icorderi! |
Add warning and debug information when `cargo metadata` fails
This two produce different sets of documentation:
and:
Doing
build --release
produces the complete and expected documentation while simply doingbuild
is missing several types and modules.I'm not sure if this is expected behavior or a very peculiar bug.
This can be consistently reproduced on this project, at least by this commit.
Looking at the output at
./target/doc/kinetic/proto/command/index.html
will show a different set of results.The text was updated successfully, but these errors were encountered: