#1787 closed defect (wontfix)

cloud-backend: allocation checks in test_storage

Reported by: davidsarah Owned by: daira
Priority: normal Milestone: 1.15.0
Component: code-storage Version: cloud-branch
Keywords: test cloud-backend Cc:
Launchpad Bug:

Description

Some of the checks in test_storage.py were disabled for the cloud backend. Investigate why they were failing and fix.

Change History (6)

comment:1 Changed at 2012-07-03T15:22:11Z by davidsarah

  • Owner set to davidsarah
  • Status changed from new to assigned

comment:2 Changed at 2013-07-22T20:52:29Z by daira

  • Milestone changed from undecided to 1.12.0
  • Owner changed from davidsarah to daira
  • Status changed from assigned to new

comment:3 Changed at 2016-03-22T05:02:25Z by warner

  • Milestone changed from 1.12.0 to 1.13.0

Milestone renamed

comment:4 Changed at 2016-06-28T18:17:14Z by warner

  • Milestone changed from 1.13.0 to 1.14.0

renaming milestone

comment:5 Changed at 2020-06-30T14:45:13Z by exarkun

  • Milestone changed from 1.14.0 to 1.15.0

Moving open issues out of closed milestones.

comment:6 Changed at 2020-10-30T12:35:44Z by exarkun

  • Resolution set to wontfix
  • Status changed from new to closed

The established line of development on the "cloud backend" branch has been abandoned. This ticket is being closed as part of a batch-ticket cleanup for "cloud backend"-related tickets.

If this is a bug, it is probably genuinely no longer relevant. The "cloud backend" branch is too large and unwieldy to ever be merged into the main line of development (particularly now that the Python 3 porting effort is significantly underway).

If this is a feature, it may be relevant to some future efforts - if they are sufficiently similar to the "cloud backend" effort - but I am still closing it because there are no immediate plans for a new development effort in such a direction.

Tickets related to the "leasedb" are included in this set because the "leasedb" code is in the "cloud backend" branch and fairly well intertwined with the "cloud backend". If there is interest in lease implementation change at some future time then that effort will essentially have to be restarted as well.

Note: See TracTickets for help on using tickets.