Cargo prints steps out of order

[nagisa]

Consider this output for cargo install cargo-fuzz:

    Updating registry `https://github.com/rust-lang/crates.io-index`
 Downloading cargo-fuzz v0.1.0
  Installing cargo-fuzz v0.1.0
 Downloading docopt v0.7.0
 Downloading cargo_metadata v0.1.2
 Downloading regex v0.2.1
 Downloading thread_local v0.3.3
 Downloading regex-syntax v0.4.0
 Downloading memchr v1.0.1
 Downloading utf8-ranges v1.0.0
 Downloading aho-corasick v0.6.2
 Downloading serde_derive v0.9.7
 Downloading serde_json v0.9.8
 Downloading syn v0.11.6
 Downloading serde_codegen_internals v0.13.0
 Downloading quote v0.3.13
 Downloading unicode-xid v0.0.4
 Downloading synom v0.11.0
   Compiling strsim v0.6.0
   Compiling quote v0.3.13
   Compiling libc v0.2.20
   Compiling num-traits v0.1.36
   Compiling utf8-ranges v1.0.0
   Compiling void v1.0.2
   Compiling rustc-serialize v0.3.22
   Compiling serde v0.9.7
   Compiling unreachable v0.1.1
   Compiling lazy_static v0.2.2
   Compiling regex-syntax v0.4.0
   Compiling thread-id v3.0.0
   Compiling memchr v1.0.1
   Compiling thread_local v0.3.3
   Compiling unicode-xid v0.0.4
   Compiling itoa v0.3.1
   Compiling synom v0.11.0
   Compiling aho-corasick v0.6.2
   Compiling dtoa v0.4.1
   Compiling syn v0.11.6
   Compiling serde_json v0.9.8
   Compiling regex v0.2.1
   Compiling serde_codegen_internals v0.13.0
   Compiling serde_derive v0.9.7
   Compiling docopt v0.7.0
   Compiling cargo_metadata v0.1.2
   Compiling cargo-fuzz v0.1.0
    Finished release [optimized] target(s) in 58.30 secs
  Installing #####################

Now, the first two steps say:

 Downloading cargo-fuzz v0.1.0
  Installing cargo-fuzz v0.1.0

So, it is installing the thing even before it is compiled; that’s obviously not true, so assume that its printed before all the steps that are necessary to actually install it (such as downloading dependencies and compiling the binary) are started.

However at the same time, compiling step is printed after the downloading step – which sort of is an inverse of above observation.

I feel like I’ve observed somewhat related inconsistencies while using rustbuild wherein printout Compiling crate does not necessarily reflect the fact of build for this crate being started.

[alexcrichton]

For rustbuild, you're probably running into #833

[stale]

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

• Is this still relevant?
• If so, what is blocking it?
• Is it known what could be done to help move this forward?

Thank you for contributing!

(The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.)

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

[stale]

As I didn't see any updates in 30 days I'm going to close this. Please see the previous comment for more information!