Output order does not indicate thread execution order

[deep-outcome]

As per my understanding on how parallel thread execution works there is no guarantee that thread which outputted 1ˢᵗ is that one that executed such common command 1ˢᵗ in common timeline.

I do not know exact details of stdout handle acquisition nor println! locking but I suppose this case is no exception.

Use rich diff.