facebook/sapling
1
1
Fork 0
mirror of https://github.com/facebook/sapling.git synced 2024-10-07 07:17:55 +03:00
Code Issues Projects Releases Wiki Activity

tests: guard against obsolete markers in the hg repo itself

Browse Source 
If obsolete markers appear in the hg repo (because of enabling evolve),
then tests that run hg against the hg repo itself will see warnings like:

  obsolete feature not enabled but 4 markers found!

As far as I can tell, this only occurs in test-check-code-hg.t -- in
particular, it will -not- show up on tests that run against test-created
repos, as most of the test suite does.
This commit is contained in:
Kevin Bullock 2013-02-09 13:35:45 +00:00
parent 3d65ebe9c1
commit e1f1e38c39
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
tests/test-check-code-hg.t
View File

@ -1,6 +1,6 @@
$ check_code="$TESTDIR"/../contrib/check-code.py
$ cd "$TESTDIR"/..
$ if hg identify -q > /dev/null; then :
$ if hg identify -q > /dev/null 2>&1; then :
> else
> echo "skipped: not a Mercurial working dir" >&2
> exit 80
@ -8,8 +8,9 @@
New errors are not allowed. Warnings are strongly discouraged.
$ hg manifest | xargs "$check_code" --warnings --nolineno --per-file=0 \
> || false
$ hg manifest 2>/dev/null \
> | xargs "$check_code" --warnings --nolineno --per-file=0 \
> || false
tests/test-serve.t:0:
> > kill `cat hg.pid`
don't use kill, use killdaemons.py