[ovs-dev] [PATCH v2] ovn-sbctl: eliminate a spurious test case error cause

Ryan Moats rmoats at us.ibm.com
Tue Jul 19 03:38:58 UTC 2016


"dev" <dev-bounces at openvswitch.org> wrote on 07/07/2016 04:30:01 PM:

> From: Lance Richardson <lrichard at redhat.com>
> To: dev at openvswitch.org
> Date: 07/07/2016 04:30 PM
> Subject: [ovs-dev] [PATCH v2] ovn-sbctl: eliminate a spurious test
> case error cause
> Sent by: "dev" <dev-bounces at openvswitch.org>
>
> The "ovn-sbctl" test fails occasionally due to log messages
> similar to these:
>
>   jsonrpc|WARN|unix: receive error: Connection reset by peer
>   reconnect|WARN|unix: connection dropped (Connection reset by peer)
>
> Since we're already ignoring "Broken pipe" messages in this test
> case, and the difference between EPIPE and ECONNRESET on send
> is simply a matter of whether the peer had unconsumed data
> in its receive buffer when the peer socket was closed, it should
> be OK to ignore "reset by peer" logs as well.
>
> This same type of failure has been observed in ovs-nbctl and
> ovn-vtep-controller tests, so fix it there as well.
>
> Signed-off-by: Lance Richardson <lrichard at redhat.com>
> ---

This looks simple enough, applies clean and passes unit tests,
so.  If it were a crash, I'd look for a test case, but since it isn't...

Acked-by: Ryan Moats <rmoats at us.ibm.com>



More information about the dev mailing list