tor/scripts/maint/practracker
teor cda2ff1965
practracker: Capture stderr output in test_practracker.sh
And canonicalise file paths, so that output is consistent, even in
out-of-tree builds.

Capturing stderr output produces better diagnostics.

Diagnostics for 32705.
2020-01-15 22:29:22 +10:00
..
testdata practracker: Capture stderr output in test_practracker.sh 2020-01-15 22:29:22 +10:00
.enable_practracker_in_hooks maint-0.4.2: remove ".enable_practracker_in_hooks". 2019-10-11 17:18:55 -04:00
exceptions.txt Merge branch 'stream-socks-auth' into bug19859_merged 2019-11-25 07:58:02 -05:00
includes.py Merge branch 'ticket32609_squashed' 2019-12-04 12:15:28 -05:00
metrics.py practracker: handle empty files. 2019-09-02 15:40:35 -04:00
practracker_tests.py Port practracker unit tests to python 3 2019-08-01 14:00:48 -04:00
practracker.py practracker: add a missing #. 2019-10-16 09:15:00 -04:00
problem.py practracker: An exception is "used" even when it is violated. 2019-09-18 10:28:33 -04:00
README practracker: make filename terminology uniform 2019-08-29 09:20:27 -04:00
test_practracker.sh practracker: Capture stderr output in test_practracker.sh 2020-01-15 22:29:22 +10:00
util.py practracker: Don't read editor temp files, attempt 2 2019-11-14 16:12:19 +10:00

Practracker is a simple python tool that keeps track of places where
our code is ugly, and tries to warn us about new ones or ones that
get worse.

Right now, practracker looks for the following kinds of
best-practices violations:

  .c files greater than 3000 lines long
  .h files greater than 500 lines long
  .c files with more than 50 includes
  .h files with more than 15 includes

  All files that include a local header not listed in a .may_include
  file in the same directory, when that .may_include file has an
  "!advisory" marker.

The list of current violations is tracked in exceptions.txt; slight
deviations of the current exceptions cause warnings, whereas large
ones cause practracker to fail.

For usage information, run "practracker.py --help".