rustbuild: some x.py targets no longer print their dependencies being built

[matthiaskrgr]

When running x.py install for example, x.py would previously show the build (cargo) output when building cargo during x.py install, but that is no longer the case. Is that intentional?

....
Uplifting rustc (stage1 -> stage3)
Building tool cargo (stage2 -> stage3)
Building tool cargo-credential-1password (stage2 -> stage3)
Dist cargo-1.71.0-dev-x86_64-unknown-linux-gnu
	finished in 2.176 seconds
Install cargo stage2 (Some(x86_64-unknown-linux-gnu))

[albertlarsan68]

It's not intentional AFAIK, but I don't see a recent PR that could have broken this off the top of my head.
Do you have a commit/timeframe where this worked correctly?

[matthiaskrgr]

Hmm I would guess it still worked last weekend?

[jyn514]

Are you sure cargo is actually being built? stage2 -> stage3 makes me think it's using cached stage 2 artifacts.

[matthiaskrgr]

Might be 103ed0e

[matthiaskrgr]

Yes, I can see rustc building cargo and its deps in htop while x.py does not print any updates 😅

[jyn514]

oh lol that would do it

cc @weihanglo

[weihanglo]

Sounds like we do need stream_cargo there? I'll put it back then!

[albertlarsan68]

Is there not a try_run way of doing things?

[jyn514]

Yes, there's a try_run, that would be best.