annotate tests/test-hgcia @ 10300:c437745f50ec
run-tests: split tests/blacklist in tests/blacklists/*
Following discussions with Gilles Morris [1], it seems that it is preferable to
use several blacklist files in a blacklists/ directory. It is easier to add an
unversioned file for experiments than modifying a tracked file.
Also fall back to a simpler syntax, giving up ConfigParser, now that section
names are not needed anymore.
And allow --blacklist parameter to be a complete path, instead of only one
of the filenames contained in tests/blacklists/
[1] http://www.selenic.com/pipermail/mercurial-devel/2009-December/017317.html
author |
Nicolas Dumazet <nicdumz.commits@gmail.com> |
date |
Thu, 10 Dec 2009 17:21:31 +0900 |
parents |
b80b944836ec |
children |
|
rev |
line source |
7438
|
1 #!/bin/sh
|
|
2
|
|
3 cat >> $HGRCPATH <<EOF
|
|
4 [extensions]
|
|
5 hgcia=
|
|
6
|
|
7 [hooks]
|
|
8 changegroup.cia = python:hgext.hgcia.hook
|
|
9
|
|
10 [cia]
|
|
11 user = testuser
|
|
12 project = testproject
|
|
13 test = True
|
|
14 EOF
|
|
15
|
|
16 hg init src
|
|
17 hg init cia
|
|
18
|
|
19 cd src
|
|
20 echo foo > foo
|
|
21 hg ci -Amfoo
|
|
22
|
|
23 hg push ../cia
|