TestNewFileLog svn related functional test fails sometimes

[Christian Boos]

From time to time, we still have an error in a functional test:

Add a file to the repository and verify it is in the browser ... ok
runTest (trac.versioncontrol.tests.functional.TestNewFileLog)
Verify browser log for a new file ... ERROR

...

======================================================================
ERROR: runTest (trac.versioncontrol.tests.functional.TestNewFileLog)
Verify browser log for a new file
----------------------------------------------------------------------
Traceback (most recent call last):
  File "c:\Trac\repos\trunk\trac\versioncontrol\tests\functional.py", line 93, in runTest
    revision = self._testenv.svn_add(fulltempfilename, '')
  File "c:\Trac\repos\trunk\trac\tests\functional\svntestenv.py", line 67, in svn_add
    self.call_in_workdir(['svn', 'add', filename])
  File "c:\Trac\repos\trunk\trac\tests\functional\testenv.py", line 233, in call_in_workdir
    (args, self.work_dir()))
Exception: Unable to run command ['svn', 'add', 'component1/trunk/five'] in c:\Trac\repos\trunk\testenv\workdir

testing.log shows:

127.0.0.1 - - 
Committed revision 1.
Updating '.':
A    component1
A    component1\trunk
A    component1\branches
A    component1\tags
A    component2
A    component2\trunk
A    component2\branches
A    component2\tags
Updated to revision 1.
A         component1\trunk\five
Adding         component1\trunk\five
Transmitting file data .
Committed revision 2.

Committed revision 3.
Updating '.':
A    component1\trunk\a
Updated to revision 3.

Committed revision 4.
Updating '.':
A    component1\trunk\b
Updated to revision 4.

Committed revision 5.
Updating '.':
A    component1\trunk\c
Updated to revision 5.

Committed revision 6.
Updating '.':
A    component1\trunk\d
Updated to revision 6.

and testenv/workdir/component1/trunk:

$ svn ls -v
      6 admin                 Sep 22 14:15 ./
      3 admin                 Sep 22 14:15 a/
      4 admin                 Sep 22 14:15 b/
      5 admin                 Sep 22 14:15 c/
      6 admin                 Sep 22 14:15 d/
      2 admin             637 Sep 22 14:15 five

Besides, I already recorded a similar failure a few weeks ago, and there the error was similar but not exactly the same:

======================================================================
ERROR: runTest (trac.versioncontrol.tests.functional.TestNewFileLog)
Verify browser log for a new file
----------------------------------------------------------------------
Traceback (most recent call last):
  File "c:\Trac\repos\0.12-stable\trac\versioncontrol\tests\functional.py", line 93, in runTest
    revision = self._testenv.svn_add(fulltempfilename, '')
  File "c:\Trac\repos\0.12-stable\trac\tests\functional\svntestenv.py", line 67, in svn_add
    self.call_in_workdir(['svn', 'add', filename])
  File "c:\Trac\repos\0.12-stable\trac\tests\functional\testenv.py", line 226, in call_in_workdir
    (args, self.work_dir()))
Exception: Unable to run command ['svn', 'add', 'component1/trunk/ten'] in c:\Trac\repos\0.12-stable\testenv\workdir

----------------------------------------------------------------------

In testing.log:

svn: warning: W150002: 'C:\Trac\repos\0.12-stable\testenv\workdir\component1\trunk\ten' is already under version control
svn: E200009: Could not add all targets because some targets are already versioned
svn: E200009: Illegal target for the requested operation

[Christian Boos]

Looking at the whole sequence of the functional tests, this was actually trivial.

What's perhaps less trivial is to fix the TODO: move this out to a subversion-specific testing module one can find there, and the related task of making the main functional test infrastructure independent of Subversion (for 1.0).

[Christian Boos]

Fixed in r11401.