GoogleServiceTestSetUp test isn't robust against interrupted test run
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
Symptoms
========
GoogleServiceT
Failure in test GoogleServiceTe
Failed doctest test for canonical.
File "/home/
-------
File "/home/
Failed example:
assert not service_
Exception raised:
Traceback (most recent call last):
File "/home/
File "<doctest canonical.
assert not service_
AssertionError
Diagnosis
=========
GoogleServiceTe
Possible fixes
==============
* Use a dynamic port (a stale service would waste resources but not break test runs)
* Kill off the old service more reliably even when a test run is interrupted
| Changed in launchpad-foundations: | |
| importance: | Undecided → High |
| milestone: | none → 2.1.12 |
| status: | New → Triaged |
| Changed in launchpad-foundations: | |
| milestone: | 2.1.12 → 2.2.1 |
| Changed in launchpad-foundations: | |
| importance: | High → Low |
| milestone: | 2.2.1 → none |
| importance: | Low → High |
| tags: | added: tech-debt |
| Robert Collins (lifeless) wrote | #1 |
| tags: |
added: test-system removed: lp-foundations |
| description: | updated |
The behaviour enforced by the asserts is appropriate. However, an interrupted test run shouldn't leave the ephemeral service running, and we should be using ephemeral ports etc too. So I'm going to tweak the description.