Question about subversion/tests/cmdline/tree_conflict_tests.py:ensure_tree_conflict()

[Arfrever Frehtes Taifersar Arahesis <ar...@gmail.com>]

subversion/tests/cmdline/tree_conflict_tests.py:ensure_tree_conflict() contains:

      except svntest.Failure:
        # Reason for catching exceptions here is to be able to see progress
        # during early development when a large number of sub-tests often
        # fail. When the feature is stable, the "try" and "except" can go away.
        (exc_type, exc_val) = sys.exc_info()[:2]
        print "EXCEPTION for", str(inc_action), "onto", str(loc_action) + ": ",
        for x in traceback.format_exception_only(exc_type, exc_val):
          sys.stdout.write(x)
        print

Is this code still needed?

-- 
Arfrever Frehtes Taifersar Arahesis

Re: Question about subversion/tests/cmdline/tree_conflict_tests.py:ensure_tree_conflict()

[Julian Foad <ju...@btopenworld.com>]

On Mon, 2008-10-20 at 03:40 +0200, Arfrever Frehtes Taifersar Arahesis
wrote:
> subversion/tests/cmdline/tree_conflict_tests.py:ensure_tree_conflict() contains:
> 
>       except svntest.Failure:
>         # Reason for catching exceptions here is to be able to see progress
>         # during early development when a large number of sub-tests often
>         # fail. When the feature is stable, the "try" and "except" can go away.
>         (exc_type, exc_val) = sys.exc_info()[:2]
>         print "EXCEPTION for", str(inc_action), "onto", str(loc_action) + ": ",
>         for x in traceback.format_exception_only(exc_type, exc_val):
>           sys.stdout.write(x)
>         print
> 
> Is this code still needed?

No, it isn't. Thanks for noticing.

I have deleted it in r33773.

- Julian



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org