[TIP] virtualenv 1.11 causes tox to fail while installing dependencies on Windows 7

[Chris Withers]

Hi Holger,

One thing to note: virtualenv 1.11 was released on 2014-01-02 and 
appears to tie in nicely with when all of my problems started.

How can I figure out what's going wrong with it?

Chris

On 12/01/2014 23:00, Chris Withers wrote:
> Hi Holger,
>
> Not a lot:
>
> C:\Jenkins\workspace\testfixtures-tox\96d5fcfe>C:\Jenkins\shiningpanda\jobs\a674
>
> d17c\tools\Scripts\python.exe -c "import tox; tox.cmdline();" -c tox.ini
> -e 2.7-
> not -vv
>    removing C:\Jenkins\workspace\testfixtures-tox\96d5fcfe\.tox\log
> using tox.ini: C:\Jenkins\workspace\testfixtures-tox\96d5fcfe\tox.ini
> using tox-1.6.1 from
> C:\Jenkins\shiningpanda\jobs\a674d17c\tools\lib\site-packag
> es\tox\__init__.py
> determining C:\Jenkins\workspace\testfixtures-tox\96d5fcfe\testfixtures*
> using package
> 'C:\\Jenkins\\workspace\\testfixtures-tox\\96d5fcfe\\testfixtures-
> 3.0.1.tar.gz', skipping 'sdist' activity
> 2.7-not start: getenv
> C:\Jenkins\workspace\testfixtures-tox\96d5fcfe\.tox\2.7-no
> t
> 2.7-not create: C:\Jenkins\workspace\testfixtures-tox\96d5fcfe\.tox\2.7-not
>    removing C:\Jenkins\workspace\testfixtures-tox\96d5fcfe\.tox\2.7-not
> setting
> PATH=C:\Jenkins\workspace\testfixtures-tox\96d5fcfe\.tox\2.7-not\Scripts
> ;C:\Program Files (x86)\PC Connectivity Solution\;C:\Program Files
> (x86)\ATI Str
> eam\bin\x86_64;C:\Program Files (x86)\ATI
> Stream\bin\x86;C:\Windows\system32;C:\
> Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\
>
> Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program
> Files\Tortoi
> seSVN\bin;C:\Program Files (x86)\PuTTY;C:\Program Files
> (x86)\TortoiseHg\;C:\Pro
> gram Files (x86)\PostgreSQL Frontend\bin;C:\Program Files
> (x86)\Calibre2\;C:\Pro
> gram Files (x86)\QuickTime\QTSystem\
>    C:\Jenkins\workspace\testfixtures-tox\96d5fcfe\.tox$
> c:\python27\python.exe C:
> \Jenkins\shiningpanda\jobs\a674d17c\tools\lib\site-packages\virtualenv.py --setu
>
> ptools --python c:\python27\python.exe 2.7-not
>  >C:\Jenkins\workspace\testfixture
> s-tox\96d5fcfe\.tox\2.7-not\log\2.7-not-0.log
> 2.7-not installdeps: nose, nose_fixes, nose-cov, mock, manuel
> setting
> PATH=C:\Jenkins\workspace\testfixtures-tox\96d5fcfe\.tox\2.7-not\Scripts
> ;C:\Program Files (x86)\PC Connectivity Solution\;C:\Program Files
> (x86)\ATI Str
> eam\bin\x86_64;C:\Program Files (x86)\ATI
> Stream\bin\x86;C:\Windows\system32;C:\
> Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\
>
> Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program
> Files\Tortoi
> seSVN\bin;C:\Program Files (x86)\PuTTY;C:\Program Files
> (x86)\TortoiseHg\;C:\Pro
> gram Files (x86)\PostgreSQL Frontend\bin;C:\Program Files
> (x86)\Calibre2\;C:\Pro
> gram Files (x86)\QuickTime\QTSystem\
> ERROR: could not install deps [nose, nose_fixes, nose-cov, mock, manuel]
> 2.7-not finish: getenv after 6.32 seconds
> __________________________________ summary
> ___________________________________
> ERROR:   2.7-not: could not install deps [nose, nose_fixes, nose-cov,
> mock, manu
> el]
>
> I checked and none of nose, nose_fixes, nose-cov, mock, manuel have had
> releases that tie up with when all my windows tox jobs started failing,
> which was since early Jan 2014.
>
> But tox --version reports 1.6.1, which is also older than a couple of
> weeks, so I'm really struggling. How can I get more info about what went
> wrong? The error message still isn't very helpful :-/
>
> Chris
>
> On 06/01/2014 10:41, holger krekel wrote:
>> Hi Chris,
>>
>> don't know.  What does output of "tox -vv" print?
>>
>> holger
>> On Sun, Jan 05, 2014 at 10:43 +0000, Chris Withers wrote:
>>> Hi Holger,
>>>
>>> What is tox trying to tell me here?
>>>
>>> Okay, so deps couldn't be installed, but why? How can I get more
>>> information?
>>>
>>> It appears that any tox jobs on this Windows node are failing in the
>>> same way. Any ideas on what to do to resolve?
>>>
>>> Chris
>>>
>>> On 05/01/2014 10:40, support at simplistix.co.uk wrote:
>>>> [96d5fcfe] $ cmd.exe /C
>>>> '"C:\Jenkins\shiningpanda\jobs\a674d17c\tools\Scripts\python.exe -c
>>>> "import tox; tox.cmdline();" -c tox.ini && exit %%ERRORLEVEL%%"'
>>>> 2.7-not
>>>> create:<http://jenkins.simplistix.co.uk/job/testfixtures-tox/./COMPONENTS=not,PYTHON=2.7,label=windows/ws/.tox\2.7-not>
>>>>
>>>> 2.7-not installdeps: nose, nose_fixes, nose-cov, mock, manuel
>>>> ERROR: could not install deps [nose, nose_fixes, nose-cov, mock,
>>>> manuel]
>>>
>>> --
>>> Simplistix - Content Management, Batch Processing & Python Consulting
>>>             - http://www.simplistix.co.uk
>>>
>>
>> ______________________________________________________________________
>> This email has been scanned by the Symantec Email Security.cloud service.
>> For more information please visit http://www.symanteccloud.com
>> ______________________________________________________________________
>>
>

-- 
Simplistix - Content Management, Batch Processing & Python Consulting
            - http://www.simplistix.co.uk