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 ]

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 ]

run-tests: patch over py2.4 proc.wait() race [ original upstream message ]

cleanup: drop unused variables and an unused import [ original upstream message ]

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 ]

Merge with stable

cleanup: remove unused imports detected by pyflakes [ original upstream message ]

Merge with stable

run-tests: sort missing files first instead of raising an error sort first for early telling typos in test names [ original upstream message ]

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 ]

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 ]

Merge with stable

run-tests: simplify interrupted message [ original upstream message ]

run-tests: remove spurious disable of --time with --debug [ original upstream message ]

run-tests: always gather runtimes [ original upstream message ]

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 ]

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 ]

run-tests: open hgrc file only for writing The file is not read here. Opening with "w+" is unnecessary. [ original upstream message ]

Merge with stable

run-tests: make --noskips work [ original upstream message ]

Merge with stable

run-tests: add --loop support This makes it easy to run tests repeatedly at high loads to look for test failures. [ original upstream message ]

run-tests: --interactive and --jobs no longer conflict [ original upstream message ]

run-tests: sort certain slow tests earlier by keyword There are a few tests that evade the size heuristic [ original upstream message ]

run-tests: drop unused resultslock [ original upstream message ]

run-tests: drop options.child and users [ original upstream message ]

run-tests: remove runchildren, now unused [ original upstream message ]

run-tests: schedule largest tests first [ original upstream message ]

run-tests: introduce thread scheduler [ original upstream message ]

run-tests: use count to calculate port to use This will keep threads from using the same server ports [ original upstream message ]

run-tests: introduce threadtmp directory [ original upstream message ]

run-tests: add abort flag This will be used to help threads clean up gracefully [ original upstream message ]