Calling start_windmill() a second time doesn't produce sane settings

Bug #430553 reported by Björn Tillenius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Björn Tillenius

Bug Description

In our test suite we call start_windmill() before starting the tests for a specific domain (e.g. bugs.launchpad.dev), and call teardown() when the tests are finished. However, calling start_windmill() works only the first time. The second time, most of the settings are wrong.

Related branches

Changed in windmill:
importance: Undecided → Unknown
status: New → Unknown
Changed in windmill:
status: Unknown → New
tags: added: story-windmill-layer
Changed in launchpad-foundations:
milestone: none → 3.1.10
Revision history for this message
Diogo Matsubara (matsubara) wrote : Bug fixed by a commit
Changed in launchpad-foundations:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in launchpad-foundations:
importance: Undecided → High
Changed in launchpad-foundations:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.