Part of canonical.launchpad.daemons.tachandler View In Hierarchy
Known subclasses: canonical.buildd.tests.harness.BuilddSlaveTestSetup, canonical.database.ftests.PortForwardTestSetup, canonical.librarian.ftests.harness.TacLibrarianTestSetup, canonical.zeca.ftests.harness.ZecaTestSetup, lp.buildmaster.tests.harness.BuilddManagerTestSetup, lp.codehosting.tests.servers.CodeHostingTac, lp.poppy.tests.test_poppy.PoppyTac, lp.registry.tests.test_distributionmirror_prober.HTTPServerTestSetup
You can override setUpRoot to set up a root directory for the daemon.
Method | setUp | Undocumented |
Method | tearDown | Undocumented |
Method | killTac | Kill the TAC file if it is running. |
Method | sendSignal | Send the given signal to the tac process. |
Method | setUpRoot | Override this. |
Method | root | Undocumented |
Method | tacfile | Undocumented |
Method | pidfile | Undocumented |
Method | logfile | Undocumented |
Method | _hasDaemonStarted | Has the daemon started? |
Method | _waitForDaemonStartup | Wait for the daemon to fully start. |
Startup is recognized by the appearance of LOG_MAGIC in the log file.
Times out after 20 seconds. If that happens, the log file content will be included in the exception message for debugging purpose.
Raises | TacException | Timeout. |
This should be able to cope with the root already existing, because it will be left behind after each test in case it's needed to diagnose a test failure (e.g. log files might contain helpful tracebacks).