Open
Description
openedon Jul 4, 2020
For crates which time out due to resource limits, there is very little indication of why: the logs show only 'process exited with signal SIGKILL'. It would be ideal to say why the process was killed and how much time and memory were used.
I wonder if docs.rs can use this same trick with /usr/bin/time -v?
$ cargo clean
$ /usr/bin/time -v cargo doc --no-deps -p termwiz
...
Command being timed: "cargo doc --no-deps -p termwiz"
User time (seconds): 90.74
System time (seconds): 6.77
Percent of CPU this job got: 456%
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:21.37
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 3810736
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 0
Minor (reclaiming a frame) page faults: 2504493
Voluntary context switches: 4301
Involuntary context switches: 50046
Swaps: 0
File system inputs: 0
File system outputs: 705048
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0Originally posted by @wez in #842 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment