juju-quickstart has no dep8 tests so can break when juju-core changes
Bug #1325013 reported by
Robie Basak
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-quickstart |
Triaged
|
High
|
Unassigned | ||
| juju-quickstart (Ubuntu) |
Triaged
|
High
|
Unassigned | ||
Bug Description
Late last cycle, a juju-core upload broke juju-quickstart in bug 1306537, but this was not picked up. A dep8 test for juju-quickstart would be able to automatically test and hold juju-core in -proposed until juju-quickstart is updated in tandem, should this arise again in the future.
To make this happen, I'll need to make juju-quickstart run non-interactively. I haven't checked to see if it can already do this, or if I need to make a feature request.
| Changed in juju-quickstart: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Robie Basak (racb) wrote | #1 |
Revision history for this message
| Francesco Banconi (frankban) wrote | #2 |
To post a comment you must log in.
Update. I've added a dep8 smoke test to juju-quickstart in Vivid, but it is failing due to a proxy error - something to do with the environment it runs in: https:/
I'll need to investigate this next, but I'm leaving it for now.