Mercurial > evolve
annotate tests/test-check-pyflakes.t @ 3782:27cf636b2f4d stable
next: respect `commands.update.check` config option in `hg next` (issue5808)
`commands.update.check` config option determines what level of checking should
be done when we update to another revision. When we set this config option to
`noconflict`, it updates your working directory to a specified revision only
when there will be no conflicts which is a very nice behavior.
This patch adds logic to respect the config option so that we can have that nice
behavior with `hg next` too.
It turns out, we just needed to use hg.updatetotally() and add some cases to
check config option.
Right now, we only respect the config if value is set to `noconflict`. Otherwise
we fallback to the default behavior.
This is a part of fixing issue5808. Test changes demonstrate the fix.
author | Pulkit Goyal <7895pulkit@gmail.com> |
---|---|
date | Sun, 03 Jun 2018 02:37:13 +0530 |
parents | 01ee3e155726 |
children | 824fcba2cdb4 |
rev | line source |
---|---|
1930 | 1 #require test-repo pyflakes |
2 | |
3 Copied from Mercurial core (60ee2593a270) | |
4 | |
5 $ cd "`dirname "$TESTDIR"`" | |
6 | |
7 run pyflakes on all tracked files ending in .py or without a file ending | |
8 (skipping binary file random-seed) | |
9 | |
2121
01ee3e155726
checks: correct the shebang line filtering for python files
Matt Harbison <matt_harbison@yahoo.com>
parents:
2107
diff
changeset
|
10 $ hg locate 'set:(**.py or grep("^#!.*python")) - removed()' 2>/dev/null \ |
2107
42f3329aa144
checks: do not run pyflake on removed file
Pierre-Yves David <pierre-yves.david@ens-lyon.org>
parents:
2038
diff
changeset
|
11 > | xargs pyflakes 2>/dev/null |