Making check in tests ========================= shorten error tests ========================== + Running error tests against mono benchmark files... shorten: cannot use -e, -k or -i with data on standard input shorten: for more information use: shorten -h cat: write error: Broken pipe shorten: cannot use -e, -k or -i with data on standard input shorten: for more information use: shorten -h shorten: cannot use -e, -k or -i with data on standard input shorten: for more information use: shorten -h cat: write error: Broken pipe shorten: will not input data from a tty shorten: for more information use: shorten -h shorten: will not input data from a tty shorten: for more information use: shorten -h shorten: will not input data from a tty shorten: for more information use: shorten -h ajkg^B<FB>r<E0>^S<F2>J<B2><A5>I<A3>Q<AF>^W<F8>^D^B<AF>A<AB>Ql<D6>ۤ<82>!^@<80>@ ^L^B!'<80>@$^T<E8>^D^B^E^@<88>@,<96>A5><86><A9>^?<80>@,`^S<AE><AB><9D>]"L<D2>^U <9F>)!-<E8> -<B3>K{[z%<BC><82>U<E4>D<92><F3>h<AC><EB><E4><92>"O6M^Y<92>T<97>^R<(<B0><U+0616><BB><BF>I^Q ***** BINARY-LIKE OUTPUT OMITTED ***** S<A9>h<9A>%^Q[<DE><F5><97>3@<81>#3^QK$<A1><A4>T<B3><ED><CE>O<84><8C><E4>"^Y<F1>^D<A5><AF>^H<8B>|<CF>^S=<84><90>FAIL: test-errors.sh But if I cd into {$PORTAGE_TMPDIR}/media-sound/shorten-3.6.0/work/shorten-3.6.0/tests and run make check by hand it tells me everything went fine. So it seems like portage issues make check in a wrongfully way. The only diffrense I can se in the output before the breakage with the one that works is those: cat: write error: Broken pipe so maybe it 'cat' a wave-file or something alike?
well, shorten should refuse to output it, but as it doesn't detect a tty for stdout (probably because of portage logging) it thinks its ok to output there, thus the test fails. Fixed anyway, disabling the offending tests
