[Development] Periodical digest from CI (04/2013)

[Sarajärvi Tony]

When I googled for reasons, I found out that there are many. The obvious ones would be related to PATH, but that doesn't explain why it doesn't happen every time. Nor have I been able to fix the problem with changing the PATH.

I have since created 2 new setups. A windows 7 64bit and a windows 8 32 bit. Just as a try to narrow down the problem to either Win8 or the 64bit. Neither worked, since both of these two new computers pass and don't reproduce the problem.

Debugging this is hard. It's like quantum mechanics, try to look at something and you change the setup so that it doesn't reproduce. Because of this, I've set up a task for myself to just recreate Win8 64bit from scratch, and see if it still occurs.

-Tony

-----Original Message-----
From: development-bounces+tony.sarajarvi=digia.com at qt-project.org [mailto:development-bounces+tony.sarajarvi=digia.com at qt-project.org] On Behalf Of Thiago Macieira
Sent: 12. huhtikuuta 2013 17:52
To: development at qt-project.org
Subject: Re: [Development] Periodical digest from CI (04/2013)

On sexta-feira, 12 de abril de 2013 12.36.45, Sarajärvi Tony wrote:
> As the cmd.exe problem for our Windows 8 builds still exists, we set up two
> new servers just to narrow down the problem.

I've wondered about that one every time one of the builds fails after 
compiling everything because perl can't find cmd.exe.

How is that possible? Do you have any theories how that can happen? Did the 
build somehow erase cmd.exe during the build? Did PATH somehow get corrupted? 
Windows 8 bug?

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center