On 26/07/16 07:43, Frank Ch. Eigler wrote:
...
Weird. On my F24 workstation, it works fine with both python{2,3}.
python-2.7.12-1.fc24.x86_64
python2-requests-2.10.0-2.fc24.noarch
python3-3.5.1-12.fc24.x86_64
python3-requests-2.10.0-2.fc24.noarch
It gets even weirder ... something else is in play here ... do you have
PCP commit e372000480 included (Nathan's investigations yesterday
suggested this was somehow implicated)?
Initially, my F24 platform had ...
kenj@vm03:~/src/pcp/qa$ rpm -q python python3 python2-requests
python3-requests
python-2.7.11-5.fc24.x86_64
python3-3.5.1-8.fc24.x86_64
python2-requests-2.10.0-2.fc24.noarch
python3-requests-2.10.0-2.fc24.noarch
and qa/662 dies as per the attached 662.out.bad.1
THen I upgraded to the lastest F24 bits ...
kenj@vm03:~/src/pcp/qa$ rpm -q python python3 python2-requests
python3-requests
python-2.7.12-1.fc24.x86_64
python3-3.5.1-12.fc24.x86_64
python2-requests-2.10.0-2.fc24.noarch
python3-requests-2.10.0-2.fc24.noarch
which looks a lot like yours, but qa/662 fails with exactly the same
failure signature.
662.out.bad.1
Description: Text document
|