bors 420f9ec576 Auto merge of #5456 - LukasKalbertodt:patch-1, r=matklad
Show elapsed time in minutes if >= 60 secs

In large projects with long compile times, seeing "428.65 secs" isn't as clear to humans as seeing the number of minutes (and seconds).

**Old**:
```
Finished dev [unoptimized + debuginfo] target(s) in 2.23 secs
Finished dev [unoptimized + debuginfo] target(s) in 63.94 secs
Finished dev [unoptimized + debuginfo] target(s) in 428.65 secs
```

**New**:
```
Finished dev [unoptimized + debuginfo] target(s) in 2.23s
Finished dev [unoptimized + debuginfo] target(s) in 1m 3.94s
Finished dev [unoptimized + debuginfo] target(s) in 7m 8.65s
```

Note that I also changed `secs` to `s`, because `7 mins 8.65 secs` and `7m 8.65 secs` both look strange IMO. But if you disagree and you'd prefer `secs`, just tell me and I'll change it.

I *didn't* add a check for `secs >= 3600` to print the time in hours. I *hope* this is not necessary...
2018-05-02 17:17:27 +00:00
..
2018-04-27 13:42:30 -07:00
2018-03-14 17:48:23 -07:00
2018-03-14 17:48:23 -07:00
2018-04-27 13:42:30 -07:00
2018-05-01 17:38:22 +02:00
2018-03-14 17:48:23 -07:00
2018-03-14 17:48:23 -07:00
2018-03-14 17:48:23 -07:00
2018-03-25 12:53:22 +02:00
2018-03-14 17:48:23 -07:00
2018-03-14 17:48:23 -07:00
2018-04-27 13:22:00 -07:00
2018-05-02 07:34:19 -07:00
2018-04-05 03:45:15 +02:00
2018-03-14 17:48:23 -07:00
2018-04-11 23:16:17 +02:00
2018-03-14 17:48:23 -07:00
2018-03-14 17:48:23 -07:00
2018-03-14 17:48:23 -07:00
2018-05-01 09:39:22 +08:00
2018-04-22 12:14:21 -07:00
2018-03-14 17:48:23 -07:00
2018-04-27 13:42:30 -07:00
2018-03-14 17:48:23 -07:00
2018-04-18 15:08:18 +07:00
2018-04-28 17:57:03 +03:00
2018-04-18 17:44:23 +03:00
2018-04-27 13:42:30 -07:00
2018-04-19 19:19:11 +01:00
2018-03-14 17:48:23 -07:00
2018-03-14 17:48:23 -07:00
2018-03-24 20:04:19 +01:00
2018-03-14 17:48:23 -07:00
2018-03-14 17:48:23 -07:00
2018-03-14 17:48:23 -07:00