error messages for collect phase failures are unhelpful

[Barry Price]

This may be related to LP#1646426, but relates to the actual output rather than the behaviour.

I've likely changed a source to one of the charms in my collect phase since the previous run, but in this situation Mojo simply reports:

2017-06-01 02:35:43 [ERROR] Error during collect phase

It would be much more helpful if Mojo could at least let me know which charm it failed to collect.

[Paul Gear (paulgear)]

This is pretty important when you're coming to a spec that you haven't touched and you're not sure which thing was changed from the live version.

[Jacek Nykis (jacekn)]

On top of that full log does not indicate what the problem might be:

2017-09-20 12:44:15 [INFO] Using pre-existing container class lxc
2017-09-20 12:44:16 [INFO] Rsyncing /home/<redacted>
2017-09-20 12:44:16 [INFO] Building resource tree
2017-09-20 12:44:17 [INFO] nrpe is up to date from url cs:nrpe-31, skipping.
2017-09-20 12:44:17 [INFO] landscape-client is up to date from url cs:landscape-client-28, skipping.
2017-09-20 12:44:17 [INFO] Skipping existing dest jenkins because it looks like a bzr or git branch
2017-09-20 12:44:17 [INFO] canonical-livepatch is up to date from url cs:~livepatch-charmers/canonical-livepatch-44, skipping.
2017-09-20 12:44:20 [INFO] Pulling turku-agent from parent (bzr+ssh://bazaar.launchpad.net/~canonical-sysadmins/canonical-is-charms/turku-agent)
2017-09-20 12:44:20 [INFO] Pulling ubuntu from parent (bzr+ssh://bazaar.launchpad.net/~canonical-sysadmins/canonical-is-charms/ubuntu)
2017-09-20 12:44:23 [INFO] ubuntu is at revno 7
2017-09-20 12:44:23 [INFO] turku-agent is at revno 8
2017-09-20 12:44:23 [ERROR] Error during collect phase

My best guess is that it's "Skipping existing dest..." line but that's only INFO

[Tom Haddon (mthaddon)]

This has been packaged and released.