Comment 0 for bug 306246

GoogleServiceTestSetup doesn't recover gracefully from an interrupted test run. If the service is still running from a previous test run, it fails, instead of simply killing the service and continuing.

 GoogleServiceTestSetup (canonical.launchpad.testing.tests.googleserviceharness)

Failure in test GoogleServiceTestSetup (canonical.launchpad.testing.tests.googleserviceharness)
Failed doctest test for canonical.launchpad.testing.tests.googleserviceharness.GoogleServiceTestSetup
  File "/home/buildbot/slaves/launchpad/full/build/lib/canonical/launchpad/testing/tests/googleserviceharness.py", line 18, in GoogleServiceTestSetup

----------------------------------------------------------------------
File "/home/buildbot/slaves/launchpad/full/build/lib/canonical/launchpad/testing/tests/googleserviceharness.py", line 25, in canonical.launchpad.testing.tests.googleserviceharness.GoogleServiceTestSetup
Failed example:
    assert not service_is_available() # Sanity check.
Exception raised:
    Traceback (most recent call last):
      File "/home/buildbot/slaves/launchpad/full/build/utilities/../lib/zope/testing/doctest.py", line 1360, in __run
        compileflags, 1) in test.globs
      File "<doctest canonical.launchpad.testing.tests.googleserviceharness.GoogleServiceTestSetup[2]>", line 1, in ?
        assert not service_is_available() # Sanity check.
    AssertionError