Re: [PATCH] Ignore "yes: standard output: Broken pipe" errors

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]



On Tue, Jul 25, 2017 at 04:33:20PM +0200, Jan Kara wrote:
> Recently, some tests started failing because they had
> 
> yes: standard output: Broken pipe
> 
> in their output. Fix the problem by discarding errors from yes(1)
> program.
> 
> Signed-off-by: Jan Kara <jack@xxxxxxx>
> ---
>  common/rc         | 12 ++++++------
>  tests/generic/081 |  2 +-
>  tests/generic/108 |  2 +-
>  3 files changed, 8 insertions(+), 8 deletions(-)

I'm wondering which case failed for you and what's the diff output and
.full file? And what change caused the failure for you? Because I didn't
see any failure on my RHEL7 box nor Fedora rawhide box. I compiled
latest yes from coreutils git repo and didn't hit the error either.

So I suspect that it might be other commands in the pipeline that failed
and caused the broken pipe.

Thanks,
Eryu

--
To unsubscribe from this list: send the line "unsubscribe fstests" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Filesystems Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux