/charm-tools

Improve error reporting when pip fails during wheelhouse creation #126

Closed
johnsca opened this Issue Mar 11, 2016 · 0 comments

Comments

Assignees

@tvansteenburgh tvansteenburgh

Labels
charm-build
Projects
None yet
Milestone
  2.1
3 participants
@johnsca @marcoceppi @tvansteenburgh
@johnsca
Member

johnsca commented Mar 11, 2016

http://pastebin.ubuntu.com/15348471/

The output from pip is hidden unless you run with -l DEBUG and the stack trace is not a useful error message. We should catch that and report that it was pip that failed, with the output to explain why.

@johnsca johnsca added the charm-build label Mar 11, 2016

@marcoceppi marcoceppi added this to the 2.0 milestone Mar 12, 2016

@marcoceppi marcoceppi modified the milestones: 2.NEXT, 2.0 Mar 23, 2016

@marcoceppi marcoceppi assigned tvansteenburgh Mar 24, 2016

@marcoceppi marcoceppi modified the milestones: 2.1, 2.NEXT Mar 24, 2016

tvansteenburgh added a commit to tvansteenburgh/charm-tools that referenced this issue Mar 25, 2016

@tvansteenburgh
Better feedback to user when command fails 
Instead of raising a CalledProcessError, write the output of the failed
command, and the command itself, to stderr, then exit with the exit
code of the failed command.

Fixes #126.
ed59a9d

@tvansteenburgh tvansteenburgh referenced this issue Mar 25, 2016

Merged

Better feedback to user when command fails #157

tvansteenburgh added a commit to tvansteenburgh/charm-tools that referenced this issue Mar 28, 2016

@tvansteenburgh
Better feedback to user when command fails 
Instead of raising a CalledProcessError, write the output of the failed
command, and the command itself, to stderr, then exit with the exit
code of the failed command.

Fixes #126.
be67272

@tvansteenburgh tvansteenburgh closed this in #157 Mar 28, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment