functional tests fail to start on Windows

[Christian Boos]

Actually, the tracd server for the test environment fails to start:

Traceback (most recent call last):
  File "trac/tests/functional/__init__.py", line 216, in <module>
    unittest.main(defaultTest='suite')
  File "C:\Miniconda\lib\unittest\main.py", line 95, in __init__
    self.runTests()
  File "C:\Miniconda\lib\unittest\main.py", line 232, in runTests
    self.result = testRunner.run(self.test)
  File "C:\Miniconda\lib\unittest\runner.py", line 151, in run
    test(result)
  File "C:\Miniconda\lib\unittest\suite.py", line 70, in __call__
    return self.run(*args, **kwds)
  File "C:\Miniconda\lib\unittest\suite.py", line 108, in run
    test(result)
  File "C:\Miniconda\lib\unittest\suite.py", line 70, in __call__
    return self.run(*args, **kwds)
  File "C:\projects\trac\trac\test.py", line 158, in run
    self.setUp()
  File "trac/tests/functional/__init__.py", line 144, in setUp
    self._testenv.start()
  File "C:\projects\trac\trac\tests\functional\testenv.py", line 265, in start
    cwd=self.command_cwd)
  File "C:\Miniconda\lib\subprocess.py"
, line 702, in __init__
    errread, errwrite), to_close = self._get_handles(stdin, stdout, stderr)
  File "C:\Miniconda\lib\subprocess.py", line 823, in _get_handles
    p2cread = _subprocess.GetStdHandle(_subprocess.STD_INPUT_HANDLE)
WindowsError: [Error 6] The handle is invalid
Makefile:350: recipe for target 'functional-test' failed

Seen in AppVeyor build trunk.42:

• ​Python 2.7.11 32-bits (Conda),
• ​Python 2.6.6 32-bits,
• ​Python 2.6.6 64-bits

We don't see it for the other Python 2.7 builds because there we simply don't reach the functional test stage, as we still have unit-test errors!

Quite similar to what was seen with Git and reported in #12304.

[Christian Boos]

(got it wrong, it's not just 2.7 32-bits failing, all versions have the problem)

[Christian Boos]

The problem went away.

One change is that there are now two runs (make unit-test, then make functional-test), but I don't see how this could change the behavior.

Anyway, it will still be time to reopen and dig deeper when the problem reappears.