Wed, 18 Jun 2014 13:47:14 -0500 tests: ignore missing file with PYTHONDONTWRITEBYTECODE (issue4239) stable
Matt Mackall <mpm@selenic.com> [Wed, 18 Jun 2014 13:47:14 -0500] rev 21760
tests: ignore missing file with PYTHONDONTWRITEBYTECODE (issue4239)
Mon, 16 Jun 2014 13:30:46 -0500 hgweb: avoid initialization race (issue4280) stable
Matt Mackall <mpm@selenic.com> [Mon, 16 Jun 2014 13:30:46 -0500] rev 21759
hgweb: avoid initialization race (issue4280)
Mon, 16 Jun 2014 12:04:48 -0500 p4: accept changesets with no description (issue4282) stable
Matt Mackall <mpm@selenic.com> [Mon, 16 Jun 2014 12:04:48 -0500] rev 21758
p4: accept changesets with no description (issue4282)
Sat, 14 Jun 2014 11:56:20 -0500 merge with stable
Matt Mackall <mpm@selenic.com> [Sat, 14 Jun 2014 11:56:20 -0500] rev 21757
merge with stable
Fri, 30 May 2014 12:57:58 -0700 test-run-tests.t: test the --nodiff option
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 30 May 2014 12:57:58 -0700] rev 21756
test-run-tests.t: test the --nodiff option
Fri, 30 May 2014 12:12:12 -0700 test-run-tests.t: test the --interactive option
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 30 May 2014 12:12:12 -0700] rev 21755
test-run-tests.t: test the --interactive option
Fri, 13 Jun 2014 14:45:23 +0530 run-tests: fixes the '--interactive' option error
anuraggoel <anurag.dsps@gmail.com> [Fri, 13 Jun 2014 14:45:23 +0530] rev 21754
run-tests: fixes the '--interactive' option error This patch fixes a regression recently introduced by a refactoring. Previously when failure occurs while testing with '--interactive' was enable, it didn't prompt user by asking whether he wants to accept this failure changes or not. This was happening beacuse of the 'if' condition if ret or not self._options.interactive or \ not os.path.exists(test.errpath): Everytime failure occurs, this condition gets true and returns back even when '--interactive' is enabled. This condition don't led the function to execute further, which consist the '--interactive' functionality. Now, on failure with '--interactive' enabled, it prompts user whether he wants to accepts failure changes or not. If yes then test gets passed and returns true, else test gets failed. On every failure, results gets stored in "self.failures.append((test, reason))" But if failure changes accepted by user then test must get "pop out" from failed test list.
Fri, 13 Jun 2014 14:33:02 +0530 run-tests: checks behaviour of test on failure while testing
anuraggoel <anurag.dsps@gmail.com> [Fri, 13 Jun 2014 14:33:02 +0530] rev 21753
run-tests: checks behaviour of test on failure while testing On failure while testing, if this function "result.addFailure(self, str(e))" returns true then test get 'passed' else count as 'failed'.
Sat, 14 Jun 2014 11:49:02 -0500 revlog: fix check-code error stable
Matt Mackall <mpm@selenic.com> [Sat, 14 Jun 2014 11:49:02 -0500] rev 21752
revlog: fix check-code error
Fri, 13 Jun 2014 17:42:04 -0500 merge with stable
Matt Mackall <mpm@selenic.com> [Fri, 13 Jun 2014 17:42:04 -0500] rev 21751
merge with stable
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip