development environment broken

Bug #628120 reported by Michael Nelson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Software Center Agent
Fix Released
High
Michael Nelson

Bug Description

A new version of buildout was released in the past week, which has broken our automated development environment setup.

This is what happens:
https://pastebin.canonical.com/36561/

I spoke with Gary, and he's hoping to get a fix done today. Once that's done, we'll need to add:
include-site-packages = true

into buildout.cfg. More details here: https://pastebin.canonical.com/36564/

Revision history for this message
Michael Nelson (michael.nelson) wrote :

Thanks to help from Gary, as an intermediate fix, the following diff allows the development environment to work again (it just restricts the version of buildout to the previous version):

https://pastebin.canonical.com/36605/

But with that fix, there are many test errors (ComponentLookupErrors). At first I assumed this was related to the buildout issues, but after more help from Gary, he showed that they are not. I went back through the revisions, and it appears these errors began with revision 81: [merge] Merged in lp:~canonical-isd-hackers/software-center-agent/caching (reverting back to r80 shows tests behaving normally).

Full details from Gary: https://pastebin.canonical.com/36606/

Changed in software-center-agent:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Anthony Lenton (elachuni) wrote :

Currently in trunk the development environment builds and passes all tests if:
 - You're runing lucid
 - You have python-lazr.restful and python-lazr.restfulclient installed, and python-mock *not* installed
 - You create a virtualenv without --no-site-packages, and activate it before running make.

What I can't figure out is a set of versions of lazr.restful(client) to use with buildout as the packaged versions that come in lucid (lazr.restful 0.9.19 and lazr.restfulclient 0.9.11) don't seem to be the same code as you pull with buildout.

The related branch adjusts the buildout process to pull in lucid's exact same version numbers, but there's one test that still fails. I've tried different similar versions to no avail.

Suggestions welcome!

Changed in software-center-agent:
status: Triaged → In Progress
assignee: nobody → Michael Nelson (michael.nelson)
Changed in software-center-agent:
milestone: none → 2-implementation
Changed in software-center-agent:
status: In Progress → Fix Committed
Changed in software-center-agent:
milestone: 2-implementation → 3-internal-qa
Revision history for this message
Dave Morley (davmor2) wrote :

Instance needs a port opening in order to work correctly.

tags: added: kb-block
Revision history for this message
Michael Nelson (michael.nelson) wrote :

Hi Dave,

To run tests or to actually run a server locally?

I'd want all tests to pass without needing to open ports (should not be using anything other than the local network), but I don't expect a dev server to work out of the box with staging services etc.

Thanks!

Revision history for this message
Michael Nelson (michael.nelson) wrote :

This fix is not qa-able, as it just ensures that the development environment builds correctly. If you look at the MP most changes are in the buildout.cfg, readme and tests.

There is one change however in code that enables newer versions of lazr.restful to work too, this is the one-line addition in: 'src/softwarecenteragent/models/webservice.py'.

tags: added: qa-untestable
tags: removed: kb-block
Dave Morley (davmor2)
Changed in software-center-agent:
milestone: 3-internal-qa → 4-staging
Dave Morley (davmor2)
Changed in software-center-agent:
milestone: 4-staging → 5-production
Dave Morley (davmor2)
Changed in software-center-agent:
milestone: 5-production → 10.11.0
Changed in software-center-agent:
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.