amulet doesn't always run with latest local charm revision

Bug #1435844 reported by Corey Bryant
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Amulet
Confirmed
Undecided
Unassigned

Bug Description

Amulet 1.10.0 appears to be caching the local charm such that if I make a code change locally and commit it, then run an amulet test, the charm code that gets run on the unit does not include that commit, and so on. I think I have to push and re-branch the code to get amulet to run against the latest. I'm sure there's a directory I could delete but I haven't found it. Also, side note, it looks like amulet is leaking files such as /tmp/amulet_deployment_* and /tmp/amulet-juju-deployer-*

Anyway, this makes development really difficult.

Marco Ceppi (marcoceppi)
Changed in amulet:
status: New → Confirmed
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.