- Apr 07, 2017
-
-
Jun Wu authored
This shows how "hg status" is wrong - nothing changed but the file is labeled as "M".
-
- Apr 08, 2017
-
-
Matt Harbison authored
The full error is "No connection could be made because the target machine actively refused it".
-
Matt Harbison authored
-
Matt Harbison authored
There are various files committed above that can't be used on Windows because of the name, or being a symlink.
-
Matt Harbison authored
MSYS thinks the ':' is a Unix path separator, and replaces it with ';'.
-
- Apr 09, 2017
-
-
Matt Harbison authored
My initial expectation was that the list would be empty, and therefore detectable with {if()}. The map for {latesttag()} is populated with real values in this case (except {tag}), so it probably doesn't make any sense to change this to an empty list.
-
- Apr 06, 2017
-
-
Denis Laxalde authored
-
Denis Laxalde authored
In followlines.js, we create a <div id="followlines-tooltip"> element to draw attention of users on "followlines" feature. The element shows up on hover of source lines after one second and follows the cursor. After first click (start line selection), the text changes and indicates that next click will terminate selection.
-
- Apr 08, 2017
-
-
Gregory Szorc authored
This contains a fix for compilation on BSDs. #no-check-commit
-
- Mar 08, 2017
-
-
Olivier Trempe authored
watchman's paths encoding can differ from filesystem encoding. For example, on Windows, it's always utf-8. Before this patch, on Windows, mismatch in path comparison between fsmonitor state and osutil.statfiles would yield a clean status for added/modified files. In addition to status reporting wrong results, this leads to files being discarded from changesets while doing history editing operations such as rebase. Benchmark: There is a little overhead at module import: python -m timeit "import hgext.fsmonitor" Windows before patch: 1000000 loops, best of 3: 0.563 usec per loop Windows after patch: 1000000 loops, best of 3: 0.583 usec per loop Linx before patch: 1000000 loops, best of 3: 0.579 usec per loop Linux after patch: 1000000 loops, best of 3: 0.588 usec per loop 10000 calls to _watchmantofsencoding: python -m timeit -s "from hgext.fsmonitor import _watchmantofsencoding, _fixencoding" "fname = '/path/to/file'" "for i in range(10000):" " if _fixencoding: fname = _watchmantofsencoding(fname)" Windows (_fixencoding is True): 100 loops, best of 3: 19.5 msec per loop Linux (_fixencoding is False): 100 loops, best of 3: 3.08 msec per loop
-
- Apr 07, 2017
-
-
Ryan McElroy authored
-
Ryan McElroy authored
More tests for this flag are coming in upcoming patches.
-
Pulkit Goyal authored
On python 3, builtins.unicode does not exist.
-
Pulkit Goyal authored
urllib.parse.urlencode() returns unicodes on Python 3. This commit adds a method which will take its output and encode it to bytes so that we can use bytes consistently.
-
Pulkit Goyal authored
-
Jun Wu authored
As Yuya pointed out [1], "changeset()[0]" could be simplified to "manifestnode()". I didn't notice that method earlier. It should definitely be used - it's easier to read, and faster. [1]: https://www.mercurial-scm.org/pipermail/mercurial-devel/2017-March/095716.html
-
Jun Wu authored
"pylint --version" shows: pylint 2.0.0, astroid 1.5.0 Python 2.7.13 (default, Dec 21 2016, 07:16:46) [GCC 6.2.1 20160830] I got "Your code has been rated at 10.00/10" every time and didn't know how to turn it off. Therefore the fix.
-
Jun Wu authored
The "2>&1 | egrep ..." code is used for removing uninteresting parts from tracebacks. Now the test does not dump tracebacks, they can be removed.
-
- Apr 03, 2017
-
-
Jun Wu authored
This is similar to "revlog: use raw revisions in revdiff". revdiff() generates raw text used in revlog directly. This makes test-flagprocessor.t happy.
-
- Apr 07, 2017
-
-
Jun Wu authored
Similar to fixes in revlog.py, this patch uses "rawtext" to explicitly label contents expected to be raw, and makes sure content stored in _cache is raw text. Now test-flagprocessor.t points us to another issue.
-
Jun Wu authored
This fixes bundlerevlog.flags(rev) for any revisions provided by the bundle. Now test-flagprocessor.t points us to another issue.
-
Jun Wu authored
"baserevision" returns the text that will be used to apply deltas. Since deltas are against raw texts, "baserevision" should return raw text. Now test-flagprocessor.t points us to a new error.
-
Jun Wu authored
This shows flag processor is broken with a bundle repo. The test creates non-liner history to exercise code path where the deltaparent cannot be reused.
-
Jun Wu authored
This will force "hg bundle" to use changegroup3 in the test. It is important since only changegroup3 preserves revlog flags.
-
Jun Wu authored
Since bundle2 writes changegroup version, we can just reuse the bundle2 format for changegroup3. This won't enable the bundle command to write changegroup3 in the wild, since exchange.parsebundlespec only returns changegroup2. It unlocks tests to override exchange.parsebundlespec and get "hg bundle" write changegroup3.
-
- Apr 06, 2017
-
-
Matt Harbison authored
-
Matt Harbison authored
Duplicating entire tests just because the output is different is both error prone and can make the tests harder to read. This harnesses the existing '(?)' infrastructure, both to improve readability, and because it seemed like the path of least resistance. The form is: $ test_cmd output (hghave-feature !) # required if hghave.has_feature(), else optional out2 (no-hghave-feature2 !) # req if not hghave.has_feature2(), else optional I originally extended the '(?)' syntax. For example, this: 2 r4/.hg/cache/checkisexec (execbit ?) pretty naturally reads as "checkisexec, if execbit". In some ways though, this inverts the meaning of '?'. For '(?)', the line is purely optional. In the example, it is mandatory iff execbit. Otherwise, it is carried forward as optional, to preserve the test output. I tried it the other way, (listing 'no-exec' in the example), but that is too confusing to read. Kostia suggested using '!', and that seems fine.
-
Matt Harbison authored
Test size seems to dictate the order in which the tests are run, and the next patch will add to test-success.t. Similar to c0cecc153d25.
-
Matt Harbison authored
Previously, if a series of optional output lines marked with '(?)' had a (glob) in one of the first lines, the output would be reordered such that it came last if none of the lines were output. The (re) declaration wasn't affected, which was helpful in figuring this out. There were no tests for '(re) (?)' so add that to make sure everything plays nice.
-
- Apr 07, 2017
-
-
Pulkit Goyal authored
We have converted opts to unicodes before passing them.
-
Jun Wu authored
We have too many files, and passing them via arguments could cause strange errors on some platforms [1]. Since check-code.py can now take "-" and read file names from stdin, use it instead of xargs to avoid the argv size limit. [1]: https://www.mercurial-scm.org/pipermail/mercurial-devel/2017-April/096346.html
-
Jun Wu authored
This will be used by the next patch.
-
- Apr 06, 2017
-
-
Philippe Pepiot authored
util.timer has been introduced in ae5d60bb70c9 and used in perf.py since 22fbca1d11ed. For historical portability, forcibly define util.timer in perf.py
-
- Apr 05, 2017
-
-
Alexander Fomin authored
This patch adds --binary option to `hg diff` and `hg export` to allow more control about when binary diffs are displayed in Git mode as well as some tests to verify it behaves correctly (issue5510).
-
Alexander Fomin authored
This changeset makes patch respect -a/--text option in --git mode by aligning its behaviour with git itself.
-
- Apr 04, 2017
-
-
Yuya Nishihara authored
Mixing bytes and unicode creates a mess. Do things in bytes as possible. New sysbytes() helper only takes care of ASCII characters, but avoids raising nasty unicode exception. This is the same design principle as sysstr().
-
Pierre-Yves David authored
The patch lingered for a while and nobody noticed when it was resubmitted.
-
Pierre-Yves David authored
The patch lingered for a while and nobody noticed when it was resubmitted.
-
- Apr 03, 2017
-
-
Augie Fackler authored
Caught by the buildbot with --pure, fix suggested by indygreg.
-
Augie Fackler authored
Instead of mentioning 127.0.0.1, we should use $LOCALIP. Anytime $LOCALIP appears in output, we should make sure we use (glob) on that line of output so that weird environments that do remapping jiggery pokery (such as our FreeBSD buildbot that's in a jail) don't get spurious test failures.
-