pcp
[Top] [All Lists]

Re: [pcp] Significant Python QA regression

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] Significant Python QA regression
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 21 Jul 2016 20:10:22 -0400 (EDT)
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <579161D5.7040903@xxxxxxxxxxxxxxxx>
References: <579161D5.7040903@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: 3VWdiurPWyWJXrcxg4smTPkQ3NflSA==
Thread-topic: Significant Python QA regression
Hi Ken,

----- Original Message -----
> After the latest round of commits, vm24 (i686 openSUSE 13.1) went from 2
> failures to ...
> 
> Failures: 583 635 662 823 836 880 1038 1062 1068 1069 1070 1071 1072
> 
> at least 7 of the additional failures are of the form
> 
> SyntaxError: Non-ASCII character '\xc2' in file /usr/bin/pmrep on line 802,
> but no encoding declared; see http://www.python.org/peps/pep-0263.html for
> details
> 

I have the fix from Marko for this in my queue ... running QA now, but
all non-ASCII-related failures at least should go away shortly.

The 662 issue remains a mystery though, and seems a recent regression
unrelated to any known issue so far.  On the TODO list, but I mightn't
get to it until next week.

> 
> I know this is a recurring theme, but over a long time Python seems to
> continually be accounting for more than a fair share of QA failures ... is
> there any real prospect of this situation improving, or should I just stop
> running Python tests and leave that to someone else?
> 

They're often legitimate issues, so it'd be good if you could continue to
report 'em.  Alot of this is pmrep-related which I think is settling down
now after its recent brain transplant ... so we should see this return to
stability very soon I expect.

cheers.

--
Nathan

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