view tests/test-check-code-hg.t @ 19136:e073ac988b51

match: introduce explicitdir and traversedir match.dir is currently called in two different places: (1) noting when a directory specified explicitly is visited. (2) noting when a directory is visited during a recursive walk. purge cares about both, but commit only cares about the first. Upcoming patches will split the two cases into two different callbacks. Why bother? Consider a hypothetical extension that can provide more efficient walk results, via e.g. watching the filesystem. That extension will need to fall back to a full recursive walk if a callback is set for (2), but not if a callback is only set for (1).
author Siddharth Agarwal <sid0@fb.com>
date Sun, 28 Apr 2013 21:24:09 -0700
parents cba222f01056
children 2d03c8da7d98
line wrap: on
line source

  $ check_code="$TESTDIR"/../contrib/check-code.py
  $ cd "$TESTDIR"/..
  $ if hg identify -q > /dev/null 2>&1; then :
  > else
  >     echo "skipped: not a Mercurial working dir" >&2
  >     exit 80
  > fi

New errors are not allowed. Warnings are strongly discouraged.

  $ hg manifest 2>/dev/null \
  >   | xargs "$check_code" --warnings --nolineno --per-file=0 \
  >   || false

Check Python files without py extension

  $ cp \
  >   hg \
  >   hgweb.cgi \
  >   contrib/convert-repo \
  >   contrib/dumprevlog \
  >   contrib/hgweb.fcgi \
  >   contrib/hgweb.wsgi \
  >   contrib/simplemerge \
  >   contrib/undumprevlog \
  >   "$TESTTMP"/
  $ for f in "$TESTTMP"/*; do cp "$f" "$f.py"; done
  $ "$check_code" --warnings --nolineno --per-file=0 "$TESTTMP"/*.py \
  >   || false