Fri, 19 Jul 2013 00:37:26 +0100 Merge with stable
Christian Ebert <blacktrash@gmx.net> [Fri, 19 Jul 2013 00:37:26 +0100] rev 1288
Merge with stable
Thu, 18 Jul 2013 09:42:44 -0700 run-tests: revert previous commit, run() waits after a timeout stable
Brendan Cully <brendan@kublai.com> [Thu, 18 Jul 2013 09:42:44 -0700] rev 1287
run-tests: revert previous commit, run() waits after a timeout [ original upstream message ]
Thu, 18 Jul 2013 09:39:01 -0700 run-tests: reap timed-out zombies stable
Brendan Cully <brendan@kublai.com> [Thu, 18 Jul 2013 09:39:01 -0700] rev 1286
run-tests: reap timed-out zombies [ original upstream message ]
Sat, 13 Jul 2013 23:58:01 +0200 run-tests: generally handle line endings on windows by re stable
Simon Heimberg <simohe@besonet.ch> [Sat, 13 Jul 2013 23:58:01 +0200] rev 1285
run-tests: generally handle line endings on windows by re Recently this regexp was only appended when running a python test. When running a tsttest there was a separate handling for each line type. Simplify and unify this. [ original upstream message ]
Sat, 13 Jul 2013 23:57:55 +0200 run-tests: test for os.altsep instead of os.name when checking \ for / stable
Simon Heimberg <simohe@besonet.ch> [Sat, 13 Jul 2013 23:57:55 +0200] rev 1284
run-tests: test for os.altsep instead of os.name when checking \ for / This tells more explicitly what it is about [ original upstream message ]
Wed, 17 Jul 2013 13:42:08 -0700 run-tests: replace popen locking with a noop _cleanup handler on py24 stable
Brendan Cully <brendan@kublai.com> [Wed, 17 Jul 2013 13:42:08 -0700] rev 1283
run-tests: replace popen locking with a noop _cleanup handler on py24 This also avoids the race condition, and isn't detrimental to job scheduling. [ original upstream message ]
Wed, 17 Jul 2013 13:02:12 -0700 run-tests: only lock Popen wait/poll on python 2.4 stable
Brendan Cully <brendan@kublai.com> [Wed, 17 Jul 2013 13:02:12 -0700] rev 1282
run-tests: only lock Popen wait/poll on python 2.4 It can cause scheduling bubbles and is not necessary on newer pythons. [ original upstream message ]
Wed, 17 Jul 2013 12:45:12 -0700 run-tests: lock popen wait/poll stable
Brendan Cully <brendan@kublai.com> [Wed, 17 Jul 2013 12:45:12 -0700] rev 1281
run-tests: lock popen wait/poll In python2.4, any call to Popen() may attempt to wait on any active process, and wait is not thread-safe. Make it thread-safe. See http://bugs.python.org/issue1731717 for details. [ original upstream message ]
Tue, 16 Jul 2013 12:44:11 -0500 run-tests: patch over py2.4 proc.wait() race stable
Matt Mackall <mpm@selenic.com> [Tue, 16 Jul 2013 12:44:11 -0500] rev 1280
run-tests: patch over py2.4 proc.wait() race [ original upstream message ]
Mon, 01 Jul 2013 20:48:56 +0200 cleanup: drop unused variables and an unused import stable
Simon Heimberg <simohe@besonet.ch> [Mon, 01 Jul 2013 20:48:56 +0200] rev 1279
cleanup: drop unused variables and an unused import [ original upstream message ]
Tue, 30 Apr 2013 14:56:33 +0100 tests: AIX can't handle negative date in test-dirstate.t stable
Jim Hague <jim.hague@acm.org> [Tue, 30 Apr 2013 14:56:33 +0100] rev 1278
tests: AIX can't handle negative date in test-dirstate.t test-dirstate.t fails on AIX in the absurd date test. AIX touch errors on any date prior to 1970. AIX mktime() gives an error on such dates, so the problem is deeper than touch and attempts to work around touch in Python failed. Give up. Add an AIX test to hghave and skip the absurd date test on AIX. [ original upstream message ]
Mon, 01 Jul 2013 14:19:04 +0100 Merge with stable
Christian Ebert <blacktrash@gmx.net> [Mon, 01 Jul 2013 14:19:04 +0100] rev 1277
Merge with stable
Thu, 13 Jun 2013 01:36:58 +0200 cleanup: remove unused imports stable
Simon Heimberg <simohe@besonet.ch> [Thu, 13 Jun 2013 01:36:58 +0200] rev 1276
cleanup: remove unused imports detected by pyflakes [ original upstream message ]
Thu, 13 Jun 2013 19:37:59 +0100 Merge with stable
Christian Ebert <blacktrash@gmx.net> [Thu, 13 Jun 2013 19:37:59 +0100] rev 1275
Merge with stable
Tue, 11 Jun 2013 23:39:48 +0200 run-tests: sort missing files first instead of raising an error stable
simon@laptop-tosh [Tue, 11 Jun 2013 23:39:48 +0200] rev 1274
run-tests: sort missing files first instead of raising an error sort first for early telling typos in test names [ original upstream message ]
Sun, 09 Jun 2013 16:49:08 +0200 run-tests: call Threads constructor with keyword arguments stable
simon@laptop-tosh [Sun, 09 Jun 2013 16:49:08 +0200] rev 1273
run-tests: call Threads constructor with keyword arguments This is suggested in the python documentation (on http://docs.python.org/2/library/threading.html#thread-objects) [ original upstream message ]
Sun, 09 Jun 2013 16:42:55 +0200 run-tests: ignoring tests works again stable
simon@laptop-tosh [Sun, 09 Jun 2013 16:42:55 +0200] rev 1272
run-tests: ignoring tests works again running with --retest did not work anymore because runone still returned None for this case. But this is not allowed since 6a127fa5de23. [ original upstream message ]
Sat, 08 Jun 2013 13:46:05 +0100 Merge with stable
Christian Ebert <blacktrash@gmx.net> [Sat, 08 Jun 2013 13:46:05 +0100] rev 1271
Merge with stable
Fri, 07 Jun 2013 16:04:11 -0500 run-tests: simplify interrupted message stable
Matt Mackall <mpm@selenic.com> [Fri, 07 Jun 2013 16:04:11 -0500] rev 1270
run-tests: simplify interrupted message [ original upstream message ]
Fri, 07 Jun 2013 15:58:14 -0500 run-tests: remove spurious disable of --time with --debug stable
Matt Mackall <mpm@selenic.com> [Fri, 07 Jun 2013 15:58:14 -0500] rev 1269
run-tests: remove spurious disable of --time with --debug [ original upstream message ]
Fri, 07 Jun 2013 15:56:16 -0500 run-tests: always gather runtimes stable
Matt Mackall <mpm@selenic.com> [Fri, 07 Jun 2013 15:56:16 -0500] rev 1268
run-tests: always gather runtimes [ original upstream message ]
Wed, 05 Jun 2013 22:05:29 +0200 run-tests: when interrupted report time in failure message stable
Simon Heimberg <simohe@besonet.ch> [Wed, 05 Jun 2013 22:05:29 +0200] rev 1267
run-tests: when interrupted report time in failure message When --time is specified, the interruption message of an interrupted test is extended with the time the test has run INTERRUPTED: /path/to/tests/test-example.t (after 513 seconds) [ original upstream message ]
Wed, 05 Jun 2013 22:05:02 +0200 run-tests: report interrupted tests stable
Simon Heimberg <simohe@besonet.ch> [Wed, 05 Jun 2013 22:05:02 +0200] rev 1266
run-tests: report interrupted tests When the test run is aborted, a message is printed for each interrupted test. This is helpful when a test is hanging. example failure message: INTERRUPTED: /path/to/tests/test-example.t The message can appear before or after the line with the number of tests [ original upstream message ]
Wed, 05 Jun 2013 22:42:43 +0200 run-tests: open hgrc file only for writing stable
Simon Heimberg <simohe@besonet.ch> [Wed, 05 Jun 2013 22:42:43 +0200] rev 1265
run-tests: open hgrc file only for writing The file is not read here. Opening with "w+" is unnecessary. [ original upstream message ]
Thu, 06 Jun 2013 22:36:18 +0100 Merge with stable
Christian Ebert <blacktrash@gmx.net> [Thu, 06 Jun 2013 22:36:18 +0100] rev 1264
Merge with stable
Thu, 06 Jun 2013 14:40:26 -0500 run-tests: make --noskips work stable
Matt Mackall <mpm@selenic.com> [Thu, 06 Jun 2013 14:40:26 -0500] rev 1263
run-tests: make --noskips work [ original upstream message ]
Mon, 03 Jun 2013 09:59:32 +0100 Merge with stable
Christian Ebert <blacktrash@gmx.net> [Mon, 03 Jun 2013 09:59:32 +0100] rev 1262
Merge with stable
Sun, 02 Jun 2013 18:09:06 -0500 run-tests: add --loop support stable
Matt Mackall <mpm@selenic.com> [Sun, 02 Jun 2013 18:09:06 -0500] rev 1261
run-tests: add --loop support This makes it easy to run tests repeatedly at high loads to look for test failures. [ original upstream message ]
Sun, 02 Jun 2013 17:58:51 -0500 run-tests: --interactive and --jobs no longer conflict stable
Matt Mackall <mpm@selenic.com> [Sun, 02 Jun 2013 17:58:51 -0500] rev 1260
run-tests: --interactive and --jobs no longer conflict [ original upstream message ]
Sun, 02 Jun 2013 17:58:49 -0500 run-tests: sort certain slow tests earlier by keyword stable
Matt Mackall <mpm@selenic.com> [Sun, 02 Jun 2013 17:58:49 -0500] rev 1259
run-tests: sort certain slow tests earlier by keyword There are a few tests that evade the size heuristic [ original upstream message ]
(0) -1000 -300 -100 -50 -30 +30 +50 tip