Obviously I know that coreutils' "make check" does a lot,
but didn't realize quite how many times the programs
under test were run each time I did that.
Today I made it so each and every one of them is run via valgrind,
with output from each run going into its own file. Running the
350+ primary tests that way created over 23,000 log files.
Here are the per-program stats:
Number of times run, Name
=========================
5470 ls
2343 head
1720 wc
1704 env
1582 cat
1566 rm
718 pr
701 ln
646 touch
627 expr
540 chmod
468 sort
460 date
455 od
438 mkdir
425 uniq
389 mktemp
329 tr
302 cp
250 cut
247 sha1sum
241 mv
222 stat
179 readlink
143 base64
137 seq
135 tail
94 sleep
92 id
89 timeout
73 du
71 dd
64 tac
54 chgrp
49 join
39 unexpand
36 truncate
36 ginstall
33 chown
32 factor
31 basename
29 md5sum
27 comm
24 dirname
23 printf
22 sum
18 test
18 ptx
17 df
16 split
16 rmdir
16 nproc
15 mkfifo
14 getlimits
13 tee
13 stdbuf
13 fmt
11 paste
10 tsort
10 nice
9 shred
9 chcon
8 nohup
8 csplit
7 nl
6 shuf
6 sha512sum
6 sha384sum
6 sha256sum
6 pathchk
6 mknod
6 chroot
5 groups
5 fold
5 expand
5 dircolors
4 tty
4 sha224sum
4 pwd
3 stty
3 kill
2 runcon
1 yes
1 version
1 true
1 symlinks
1 opt
1 cap
1 atomic2
1 atomic
