cowstr failed to build on crates.io because of network error

[cehteh]

Crate name

cowstr

Build failure link

https://docs.rs/crate/cowstr/1.0.0-beta2/builds/804480

Additional details

looks there was some network glitch, can you restart doc generation?

[6] Couldn't resolve host name (Could not resolve host: index.crates.io)

[Nemo157]

There is no network access during the build. It looks like the threadcell build script attempts to run cargo metadata and fails because of that (I'm not sure why, it should have everything necessary cached from the cargo fetch we run outside the sandbox). That doesn't actually seem to fail the build though, there is another error afterwards

Failed to create logfile: Os { code: 2, kind: NotFound, message: "No such file or directory" }
/opt/rustwide/cargo-home/registry/src/index.crates.io-6f17d22bba15001f/conf_test-0.3.1/src/lib.rs:227:49

That seems to be simply a bug in conf_test, it doesn't create the directory it tries to write a log file to (normally compile_file would cause the directory to be created by the rustc invocations, but if there are none the directory won't exist).

[cehteh]

On 2023-05-03 12:00, Nemo157 wrote: There is no network access during the build. It looks like the `threadcell` build script attempts to run `cargo metadata` and fails because of that (I'm not sure why, it should have everything necessary cached from the `cargo fetch` we run outside the sandbox). That doesn't actually seem to fail the build though, there is another error afterwards

Thanks, I am figuring out what happens, also changing 'conf_test' to pass '--offline' to cargo. Strange thing is that cowstr beta1 worked..

…

``` Failed to create logfile: Os { code: 2, kind: NotFound, message: "No such file or directory" } /opt/rustwide/cargo-home/registry/src/index.crates.io-6f17d22bba15001f/conf_test-0.3.1/src/lib.rs:227:49 ``` That seems to be simply a bug in `conf_test`, it doesn't create the directory it tries to write a log file to. -- Reply to this email directly or view it on GitHub: #2122 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

[Nemo157]

Yeah, I'm not entirely sure why cargo's attempting to access the network here, afaik both builds should have been using the new sparse registry protocol since that was merged back in march, so it's not to do with that behaving differently. Using --offline should hopefully avoid it.

[cehteh]

On 2023-05-03 12:16, Nemo157 wrote: Yeah, I'm not entirely sure why cargo's attempting to access the network here, afaik both builds should have been using the new sparse registry protocol since that [was merged](rust-lang/cargo#11791) back in march, so it's not to do with that behaving differently. Using `--offline` should hopefully avoid it

i am first improving conf_test its was once made as an hack and i recently using it again. It certainly needs some fixes.

…

-- Reply to this email directly or view it on GitHub: #2122 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

[syphar]

@cehteh @Nemo157 I see the latest beta-builds are passing now.

So is this still an open issue here?

[cehteh]

all ok now i changed a lot stuff in the crate