watchdog tests leave open twisted object in reactor (lucid)

Bug #920673 reported by David Britton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
Invalid
Low
Unassigned

Bug Description

===============================================================================
[ERROR]: landscape.tests.test_watchdog.DaemonTest.test_start_process_with_verbose

Traceback (most recent call last):
Failure: twisted.trial.util.DirtyReactorAggregateError: Reactor was unclean.
Selectables:
<twisted.internet.process.ProcessReader object at 0x2570e90>
<twisted.internet.process.ProcessWriter object at 0x2570e50>
<twisted.internet.process.ProcessReader object at 0x2570ed0>
-------------------------------------------------------------------------------

===============================================================================
[ERROR]: landscape.tests.test_watchdog.DaemonTest.test_wait_for_process

Traceback (most recent call last):
Failure: twisted.trial.util.DirtyReactorAggregateError: Reactor was unclean.
Selectables:
<twisted.internet.process.ProcessReader object at 0x1c01890>
<twisted.internet.process.ProcessReader object at 0x1c01a10>
<twisted.internet.process.ProcessWriter object at 0x1c01950>
===============================================================================
[ERROR]: landscape.tests.test_watchdog.DaemonTest.test_wait_or_die_dies_happily

Traceback (most recent call last):
Failure: twisted.trial.util.DirtyReactorAggregateError: Reactor was unclean.
Selectables:
<twisted.internet.process.ProcessReader object at 0x1c01690>
<twisted.internet.process.ProcessReader object at 0x1c017d0>
<twisted.internet.process.ProcessWriter object at 0x1c01110>
-------------------------------------------------------------------------------

These three tests fail off-and on (flaky) on lucid. You can get them to fail by running

trial -u -e landscape.tests.test_watchdog.DaemonTest.test_start_process_with_verbose

for each test in the list. They will eventually fail. Cannot repeat these failures on newer landscape releases. For now, I'm skipping this failure on trial with --unclean-warnings which converts these into warns.

Changed in landscape-client:
milestone: 12.01.2 → 12.02.1
Changed in landscape-client:
milestone: 12.02.1 → 12.02.2
Changed in landscape-client:
milestone: 12.02.2 → 12.03.1
Changed in landscape-client:
milestone: 12.03.1 → 12.03.2
Changed in landscape-client:
milestone: 12.03.2 → 12.04.1
Changed in landscape-client:
milestone: 12.04.1 → 12.05
Changed in landscape-client:
milestone: 12.05 → 12.12
Changed in landscape-client:
milestone: 12.12 → 13.01
Changed in landscape-client:
milestone: 13.01 → 13.02
Changed in landscape-client:
milestone: 13.02 → 13.03
Changed in landscape-client:
milestone: 13.03 → 13.04
Changed in landscape-client:
milestone: 13.04 → 13.05
Changed in landscape-client:
milestone: 13.05 → 13.06
Changed in landscape-client:
milestone: 13.06 → 13.07
Changed in landscape-client:
milestone: 13.07 → 13.08
Changed in landscape-client:
milestone: 13.08 → 13.09
Changed in landscape-client:
milestone: 13.09 → 13.09.1
Changed in landscape-client:
milestone: 13.09.1 → 13.10
Changed in landscape-client:
milestone: 13.10 → 13.11
Changed in landscape-client:
milestone: 13.11 → 13.12
Changed in landscape-client:
milestone: 13.12 → 14.01
Changed in landscape-client:
milestone: 14.01 → 14.02
Changed in landscape-client:
milestone: 14.02 → 14.03
Changed in landscape-client:
milestone: 14.03 → 14.04
Revision history for this message
🤖 Landscape Builder (landscape-builder) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

Landscape Team

Changed in landscape-client:
status: New → Invalid
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.