The launchpadlib used in pagetests uses a cache in the home directory

Bug #599886 reported by Leonard Richardson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Benji York

Bug Description

When you run pagetests locally, launchpadlib caches the documents it receives in your home directory, under .launchpadlib/cache/api.launchpad.dev/. These documents persist after the pagetest run completes. This means that if you add something to the webservice, it won't be visible until the cached WADL expires.

Every Launchpad object created within a pagetest should use a different temporary directory as its cache directory.

Related branches

Revision history for this message
Gary Poster (gary) wrote :

Triaging this as high because it will reduce the chance of developer annoyance for a very, very cheap cost.

Changed in launchpad-foundations:
importance: Undecided → High
status: New → Triaged
assignee: nobody → Benji York (benji)
Benji York (benji)
Changed in launchpad-foundations:
status: Triaged → In Progress
Benji York (benji)
Changed in launchpad-foundations:
status: In Progress → Fix Committed
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
Changed in launchpad-foundations:
milestone: none → 10.08
tags: added: qa-needstesting
Benji York (benji)
tags: added: qa-untestable
removed: qa-needstesting
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.