Opened at 2012-09-28T21:06:26Z
Closed at 2012-12-02T01:27:06Z
#1817 closed defect (fixed)
test_storage crawler tests can wedge the test machine for certain bugs in code-under-test
Reported by: | davidsarah | Owned by: | davidsarah |
---|---|---|---|
Priority: | normal | Milestone: | 1.10.1 |
Component: | code | Version: | 1.9.2 |
Keywords: | test hang | Cc: | |
Launchpad Bug: |
Description
The problem is code like this:
# now examine the state right after the first bucket has been # processed. def _after_first_bucket(ignored): initial_state = lc.get_state() if "cycle-to-date" not in initial_state: d2 = fireEventually() d2.addCallback(_after_first_bucket) return d2
Change History (2)
comment:1 Changed at 2012-09-28T23:04:09Z by davidsarah
- Milestone changed from undecided to 1.11.0
- Status changed from new to assigned
comment:2 Changed at 2012-12-02T01:27:06Z by davidsarah
- Resolution set to fixed
- Status changed from assigned to closed
Fixed in leasedb and cloud backend branches.
Note: See
TracTickets for help on using
tickets.
I'm working on replacing code like this with hooks in crawler.py that will allow it to signal the test at exactly the right points.