pcp
[Top] [All Lists]

Re: [pcp] qa/1111 failing pretty much every place it is run

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] qa/1111 failing pretty much every place it is run
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Wed, 13 Jul 2016 13:11:04 +1000
Cc: Alec Ten Harmsel <alec@xxxxxxxxxxxxxxxxxx>, PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <984783794.5564620.1468374521886.JavaMail.zimbra@xxxxxxxxxx>
References: <57858370.8030700@xxxxxxxxxxxxxxxx> <131083523.5554077.1468368582128.JavaMail.zimbra@xxxxxxxxxx> <57859524.6050605@xxxxxxxxxxxxxxxx> <984783794.5564620.1468374521886.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
On 13/07/16 11:48, Nathan Scott wrote:


----- Original Message -----
On 13/07/16 10:09, Nathan Scott wrote:
----- Original Message -----
I'm seeing 2 failure signatures.

.out.bad files attached

Any help would be appreciated as I have no clue what this test is or
should be doing.

This test is exercising the new pcp2influxdb(1) command.  There should
be a 1111.full associated with these failures, which I think we'll need
to figure out what socat sees - could you post those too please for the
two signatures?


Attached.


Taa.  I can see (at least) two different issues there -

1. We're missing a python module

(from first .full)
     import requests
ImportError: No module named 'requests'

(deb & rpm packaging should have deps in place - is this non-Linux?)

No deps for deb. And check-vm was only checking for python(2) version, but we've moved the deb build to using python3 when available and python3-requests was not installed. Fixed this and passes on one host (so far).

- I've added a _notrun() to the test to ensure "requests" module exists

2. Older requests modules

(from other .full)
requests.exceptions.ConnectionError: Max retries exceeded for url: [...]
AttributeError: 'module' object has no attribute 'HTTPBasicAuth'
User-Agent: python-requests/0.8.2^M

- Looks like HTTPBasicAuth is there since 1.0 of requests, so I've
   added a _notrun() check on that version.  Hopefully a fix for the
   "max retries"  issue is in since version 1 onward too... but that
   one may still be unresolved - lemme know?

notrun guard does not work with python3 ... (syntax error) ... fixed this and guard works on one host (so far).

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