pcp
[Top] [All Lists]

Re: More Python induced QA pain

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: More Python induced QA pain
From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Date: Mon, 25 Jul 2016 21:27:20 -0400
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <57969592.3050402@xxxxxxxxxxxxxxxx>
References: <578E9E23.9090904@xxxxxxxxxxxxxxxx> <y0mh9bdkdzj.fsf@xxxxxxxx> <5796812B.6090409@xxxxxxxxxxxxxxxx> <20160725214336.GH5274@xxxxxxxxxx> <57969592.3050402@xxxxxxxxxxxxxxxx>
User-agent: Mutt/1.4.2.2i
Hi -

On Tue, Jul 26, 2016 at 08:41:22AM +1000, Ken McDonell wrote:
> [...]
> which looks a lot like yours, but qa/662 fails with exactly the same 
> failure signature.

OK, some more googling suggests that this part was wild goose chase,
that the first exception ("buffering...") is ignorable.  The key part
is:

> QA output created by 662
> [...]
>   File "/usr/lib64/python3.5/http/client.py", line 251, in _read_status
>     raise RemoteDisconnected("Remote end closed connection without"
> http.client.RemoteDisconnected: Remote end closed connection without response
> [...]

and

> [...]
>   File "/usr/lib64/python3.5/http/client.py", line 251, in _read_status
>     raise RemoteDisconnected("Remote end closed connection without"
> requests.packages.urllib3.exceptions.ProtocolError: ('Connection aborted.', 
> RemoteDisconnected('Remote end closed connection without response',))
>  [...]

So the python code is seeing pmwebd close the connection.  Perhaps the 662.full
can help explain, or else an strace.


- FChE

<Prev in Thread] Current Thread [Next in Thread>