auto-publishing runs out of disk space

[lnicola]

https://github.com/rust-lang/rust-analyzer/actions/runs/6452854701/attempts/1

I think cargo workspaces publish rebuilds common dependencies for each published crate.

[Veykril]

Could be due to difference in default features (of dependencies) being enabled for the crates maybe?

[Veykril]

Though why is this happening now? 🤔

[lnicola]

It's been happening for a couple of weeks now, I think since we added rustc-dependencies.

[lnicola]

Actually, no, it might be since earlier. I'm not sure.

Could be due to difference in default features (of dependencies) being enabled for the crates maybe?

That would only rebuild some of the crates. Look for "Compiling libc" in this log to see what I mean. As if it's building them independently, outside the workspace.

[pksunkara]

I haven't checked this deeply, but wouldn't cargo publish command always compile freshly? or am I misunderstanding how it works?

[lnicola]

To be honest, I have no idea.

[pksunkara]

Looks like yes, it does. rust-lang/cargo#4109

[lnicola]

Ah, good find. Then I guess we can close #137?

[pksunkara]

Error: The operation was canceled.

I see the above error message in the run you started. Any reason why it was assumed to be related to disk space?

I see that timeout-minutes is not specified for the workflow, so it can't be that.

[lnicola]

Oh yeah, I just cancelled it so we don't publish anything today. But you can see in the logs that a lot of crates have been built multiple times.

[lnicola]

Worked around in #15783: https://github.com/rust-lang/rust-analyzer/actions/runs/6577778965/job/17870142380.