-
Notifications
You must be signed in to change notification settings - Fork 198
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
Windows crate docs won't build #1444
Comments
15 minutes is already pretty long ... Have you tested how long the docs take to build? How high a limit would you need? |
Maybe intermittent infrastructure failure? Building locally takes around 12 seconds.
|
This looks like a bug in your build script. I tried building the docs locally (on x86_64 linux) and it loops forever; strace shows it's trying to open /Cargo.toml over and over.
|
There's no exit condition here: https://github.com/microsoft/windows-rs/blob/2538dce6a1f071f1d4afdde7ceab0c0224e33303/crates/gen/build.rs#L13-L26 Docs.rs does not keep OUT_DIR in a subdirectory of the source folder. |
That's good to know thanks! It is incredibly frustrating that there seems to be no reliable way to determine the target dir. Am I missing something obvious? 😬 |
Hmm, I'm not sure, you'd have to ask the cargo team if they provide that for build scripts. I know for docs.rs we set CARGO_TARGET_DIR, so you could check if that's set and default to |
I already scoured the environment variables. Its not there by default. I used Obviously, a |
@kennykerr I'm pretty sure Cargo propagates CARGO_TARGET_DIR for build scripts, you should be able to test it locally. It doesn't fix the general issue but that should get docs.rs builds working. |
Yes, for doc builds but its no good if the crate itself doesn't work reliably. That's my bigger concern. |
@kennykerr hello! We temporarily blocked new builds of the This is just a temporary stopgap to avoid the docs.rs queue getting out of hand, and we'll happily remove the block as soon as you have a version number that's confirmed to be fixed. Note that the documentation of the existing versions is still up, the only thing the block does is preventing new releases from being queued for a build. |
Sorry about the noise. I've been working on this problem all day. 😉 |
No worries! I hope you'll find a solution soon |
OK, the loop is gone: https://github.com/microsoft/windows-rs/blob/master/crates/gen/build.rs And since the build script isn't needed for non-Windows builds anyway, I've This is fixed as of version 0.17.0 of windows, windows_gen, windows_macros, and windows-app crates. Apologies again for the trouble. |
For what its worth, I also switched the build to check the docs on ubuntu instead: |
Unblocked the crates and queued builds for the 0.17.0 version of those crates! Will check in a bit to ensure they finished. |
Crate name
Windows
Build failure link
https://docs.rs/crate/windows/0.14.0/builds/408479
Requested RAM limit
No response
Requested timeout
No response
Requested number of targets
No response
Why your crate needs the resource increases
The crate docs shouldn't be overly large, but the error includes mention of memory limits and timeout. Not sure why.
The text was updated successfully, but these errors were encountered: