Mon, 25 Nov 2013 22:00:46 +0100 run-tests: test result shows when a failed test could not start a server stable
Simon Heimberg <simohe@besonet.ch> [Mon, 25 Nov 2013 22:00:46 +0100] rev 1370
run-tests: test result shows when a failed test could not start a server Failing to start a server happens regularly, at least on windows buildbot. Such a failure often has nothing to do with the test, but with the environment. But half the test output can change because some data is missing. Therefore this is worth an extended error message. Detect the server failure in the diff output because it is most reliable there. Checking the output only does not show if the server failure was expected. Old failure message when server start failed: Failed test-serve.t: output changed New message: Failed test-serve.t: serve failed and output changed [ original upstream message ]
Sun, 13 Apr 2014 19:01:00 +0200 spelling: fixes from spell checker stable
Mads Kiilerich <madski@unity3d.com> [Sun, 13 Apr 2014 19:01:00 +0200] rev 1369
spelling: fixes from spell checker [ original upstream message ]
Sun, 13 Apr 2014 19:01:00 +0200 tests: warn on invalid #if directive stable
Mads Kiilerich <madski@unity3d.com> [Sun, 13 Apr 2014 19:01:00 +0200] rev 1368
tests: warn on invalid #if directive [ original upstream message ]
Sat, 12 Apr 2014 18:13:57 +0100 Merge with stable
Christian Ebert <blacktrash@gmx.net> [Sat, 12 Apr 2014 18:13:57 +0100] rev 1367
Merge with stable
Mon, 24 Mar 2014 22:12:37 -0700 run-tests: allow test paths in other directories stable
Gregory Szorc <gregory.szorc@gmail.com> [Mon, 24 Mar 2014 22:12:37 -0700] rev 1366
run-tests: allow test paths in other directories Previously, test paths were assumed to be in the same directory and wouldn't have a directory component. If a path with a directory component was specified, it would be filtered out. This change allow paths to contain directories. This in turn allows tests from other directories to be executed. Executing tests in other directories may break assumptions elsewhere in the testing code. However, on initial glance, things appear to "just work." This approach of running tests from other directories is successfully being used at https://hg.mozilla.org/hgcustom/version-control-tools/file/7085790ff3af/run-mercurial-tests.py [ original upstream message ]
Mon, 24 Mar 2014 21:52:28 -0700 run-tests: allow option parser to be extended stable
Gregory Szorc <gregory.szorc@gmail.com> [Mon, 24 Mar 2014 21:52:28 -0700] rev 1365
run-tests: allow option parser to be extended This patch moves the OptionParser population into its own function so consumers may modify the OptionParser before arguments are evaluated. This will allow consumers to add custom options, set different defaults, etc. [ original upstream message ]
Mon, 24 Mar 2014 21:41:56 -0700 run-tests: use return values instead of sys.exit stable
Gregory Szorc <gregory.szorc@gmail.com> [Mon, 24 Mar 2014 21:41:56 -0700] rev 1364
run-tests: use return values instead of sys.exit [ original upstream message ]
Mon, 24 Mar 2014 21:37:33 -0700 run-tests: Pass arguments into argument parser stable
Gregory Szorc <gregory.szorc@gmail.com> [Mon, 24 Mar 2014 21:37:33 -0700] rev 1363
run-tests: Pass arguments into argument parser Before, arguments were not passed into the optparse.OptionParser instance and were coming from sys.argv. This patch enables consumers to define the list of arguments to parse without having to adjust sys.argv. [ original upstream message ]
Sat, 22 Mar 2014 08:44:07 +0000 Merge with stable
Christian Ebert <blacktrash@gmx.net> [Sat, 22 Mar 2014 08:44:07 +0000] rev 1362
Merge with stable
Fri, 28 Feb 2014 02:09:00 +0100 tests: add run-tests --changed option for running tests changed in revisions stable
Mads Kiilerich <madski@unity3d.com> [Fri, 28 Feb 2014 02:09:00 +0100] rev 1361
tests: add run-tests --changed option for running tests changed in revisions Convenient when polishing patches and changing details of how they change test output. This will probably break in weird ways for revsets with special quoting ... but it is good enough for run-tests. Usage example: yes | ./run-tests.py -li --changed qparent [ original upstream message ]
(0) -1000 -300 -100 -10 tip