1
88%
master: 88%

Ran 14 Mar 2015 05:41PM UTC

Files 19

Run time 49s

Badge

Embed ▾

Committed 14 Mar 2015 05:20PM UTC coverage: 92.042%. Remained the same

Job # 345.1

Build Type

push

travis-ci

Committed by

oconnor663

Commit Message

stop capturing stderr in plugins

Normally plugins allow all subprocess output to go to the caller. Peru
puts all that output in the fancy display (or buffers it and prints it
later, in --verbose mode). Sometimes plugins need to read the output of
a command, though, like `git rev-parse`. In those cases, previously we
were capturing both stdout and stderr. But we shouldn't do that --
whatever ends up on stderr is likely to screw up the parsing that the
plugins was intending to do, and there's no reason to prevent stderr
messages from reaching peru's display/log. With this diff, plugins only
ever capture stdout.

Note that there's a bit of repeated code in the git/hg/svn plugins. It's
not too bad, just code for shelling out, but it does mean that we need
to make this fix in three places. Something to keep in mind.

Closes https://github.com/buildinspace/peru/issues/105.

Run Details

1330 of 1445 relevant lines covered (92.04%)

0.92 hits per line

buildinspace / peru / 345 / 1
88%
master: 88%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 345.1

buildinspace / peru / 345 / 1 88% master: 88%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 345.1

buildinspace / peru / 345 / 1
88%
master: 88%

README BADGES
x