Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 30 May 2014 12:12:03 -0700] rev 21744
test-run-tests.t: tests --jobs option
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 30 May 2014 12:11:51 -0700] rev 21743
test-run-tests.t: test --debug option
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 30 May 2014 12:11:39 -0700] rev 21742
test-run-tests.t: test selection of testfile from the command line
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 30 May 2014 12:11:17 -0700] rev 21741
test-run-tests.t: tests the --retest option
anuraggoel <anurag.dsps@gmail.com> [Thu, 12 Jun 2014 03:20:28 +0530] rev 21740
run-tests: fixes the number of tests ran when '--retest' is enabled
This patch fixes a regression recently introduced by a refactoring. (see
92a6b16c9186 and about 200 previous changesets from Gregory Szorc)
While retesting, that is when '--retest' is enabled, only failure tests run
and others either skipped or ignored.
During retesting, "result.testsRun" holds the count of failure test that has
run. But as while printing output, we have subtracted the skipped and ignored
count from "result.testsRun". Therefore, to make the count remain
the same, we need to add skipped and ignored count before printing.
anuraggoel <anurag.dsps@gmail.com> [Thu, 12 Jun 2014 02:36:52 +0530] rev 21739
run-tests: skipped test should not produce 'i' mark while retesting
When '--retest' option is enabled then skipped test should not produce 'i' mark.
This fixes a regression introduced by
92a6b16c9186 and about 200 previous
changesets from Gregory Szorc.
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 30 May 2014 12:10:56 -0700] rev 21738
test-run-tests.t: test running a failing test
Matt Mackall <mpm@selenic.com> [Fri, 13 Jun 2014 16:36:53 -0500] rev 21737
run-tests: filter whitespace at end of error diffs
Python 2.6 and 2.7 produce slightly different diff headers.
anuraggoel <anurag.dsps@gmail.com> [Thu, 12 Jun 2014 01:28:22 +0530] rev 21736
run-tests: produce '!' mark after running a failing test
This patch fixes a regression recently introduced by a refactoring (see
92a6b16c9186 and about 200 previous changesets from Gregory Szorc). '!' mark
denotes that the test gets failed while testing.
anuraggoel <anurag.dsps@gmail.com> [Thu, 12 Jun 2014 01:36:57 +0530] rev 21735
run-tests: produce error on running a failing test
This patch fixes a regression recently introduced by a refactoring (see
92a6b16c9186 and about 200 previous changesets from Gregory Szorc). It produce
an error message everytime with a test filename which gets fail while testing
except at one condition when '--nodiff' option is enabled.
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 30 May 2014 12:10:19 -0700] rev 21734
test-run-tests.t: test running a passing test
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 10 Jun 2014 14:32:52 -0700] rev 21733
run-tests: don't check for the mercurial library used when using --with-hg
In the ``--with-hg`` case, we cannot properly infer the location of the mercurial
library, so we skip the warning completely.
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 30 May 2014 12:09:49 -0700] rev 21732
test: introduce test-run-tests.t
This testfile tests the test runner itself. There were multiple regressions in the
last few weeks. Having tests would prevent this in the future.
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 30 May 2014 11:40:24 -0700] rev 21731
tests: comment the main purpose of ``test-unified-test.t``
Danek Duvall <danek.duvall@oracle.com> [Wed, 11 Jun 2014 15:31:04 -0700] rev 21730
parsers.c: fix a couple of memory leaks
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 30 May 2014 11:35:45 -0700] rev 21729
tests: rename ``test-run-tests.t`` to ``test-unified-test.t``
This ``test-run-tests.y`` is testing the unified test (.t) syntax
interpretation, not really the run-tests.py command tool itself.
Pierre-Yves David <pierre-yves.david@fb.com> [Tue, 27 May 2014 14:45:31 -0700] rev 21728
wireproto: rephrase the error message for unknown getbundle parameters
In case of an unknown parameter passed to ``getbundle``, the server prints a
message and ignores the parameter. This message was misleadingly prefixed with
"abort: ". The use of "abort: " here is clearly wrong as nothing is actually
aborted and the ``getbundle`` call proceeds without the parameter.
The message is now prefixed with "warning: " and rephrased to make it clearer
that the parameter was simply ignored.
Augie Fackler <raf@durin42.com> [Sat, 07 Jun 2014 11:32:37 -0400] rev 21727
patchbomb: reorder header insertions to clarify code
This is done as its own change to make the changes to test-patchbomb.t
easier to review.
Augie Fackler <raf@durin42.com> [Sat, 07 Jun 2014 11:06:15 -0400] rev 21726
patchbomb: always use message-id of first patch for series-id
This currently has the side effect that the 0 of N message has no
series-id. This won't matter for Mercurial's own use, but may be
undesirable for other projects depending on their workflow.
The way the header is inserted is intentionally a little funny to make
the test expectation diff easier to review.
Augie Fackler <raf@durin42.com> [Sat, 07 Jun 2014 11:30:06 -0400] rev 21725
test-patchbomb: normalize glob lines and record their construction
This makes it significantly less painful to use --interactive on
run-tests, as you can now use the recorded regular expression
substitutions to fix up the glob lines and produce zero diffs.
This also tightens the expectations of a few of the lines for the MIME
boundaries - it just seemed like the thing to do while in here and
causing some changes.
Pierre-Yves David <pierre-yves.david@fb.com> [Mon, 05 May 2014 22:51:20 -0700] rev 21724
patchbomb: includes a unique series ID in email header
Now that we have patch index and series size information, having a unique series
identifier will helps tool to glue all email back together without any
additional logic.
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 30 May 2014 11:28:48 -0700] rev 21723
color: add parenthesis to help readability
Took me a multiple attempts until my mind eventually stop reading:
auto = coloropt = 'auto'
And properly reads:
auto = colorpopt == 'auto'
So we add parenthesis to clarify.
Pierre-Yves David <pierre-yves.david@fb.com> [Sat, 31 May 2014 17:26:15 -0700] rev 21722
status: document the content of the returned tuple in the docstring
The ``status`` function returns a lot of information. We document it.
Matt Mackall <mpm@selenic.com> [Mon, 09 Jun 2014 14:11:17 -0500] rev 21721
resolve: fix grammar of no matching files message
Matt Mackall <mpm@selenic.com> [Mon, 09 Jun 2014 13:53:23 -0500] rev 21720
merge with stable
Sean Farley <sean.michael.farley@gmail.com> [Fri, 06 Jun 2014 00:21:46 -0500] rev 21719
bash_completion: add -l|--list support for shelve
This was overlooked previously and found via 'hg shelve -p -l <tab>' (to show
the diff of the shelved commit).
Yuya Nishihara <yuya@tcha.org> [Sat, 31 May 2014 21:21:06 +0900] rev 21718
workingctx: duplicate status list received at _poststatus hook
basectx.status may reorder the list after workingctx._poststatus is called,
so workingctx must copy it. Otherwise, wctx.deleted() would return "unknown"
files, for example.
Chinmay Joshi <c@chinmayjoshi.com> [Thu, 05 Jun 2014 15:24:29 +0530] rev 21717
patch: replace functions in fsbackend to use vfs
Several functions in fsbackend are replaced to use vfs functions.
vfs operations are applied on filename and path is joined by _join().
Chinmay Joshi <c@chinmayjoshi.com> [Thu, 05 Jun 2014 15:16:44 +0530] rev 21716
vfs: add unlinkpath to vfs
This patch adds unlinkpath() function in vfs to replace util.unlinkpath().
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Thu, 05 Jun 2014 22:20:32 +0900] rev 21715
shelve: add option combination tests for refactoring in succeeding patch