Since the new version, we cannot build tests anymore. The executable is still there. We have changed nothing. All properties were refreshed manually, nothing helped.
The log now says “The executable was not found at path c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\mstest.exe.”
hm ok, found a hardcoded path to mstext.exe in the Test action. Changed it to the property collector “2010”, now its working. However something seems to be different in version 1.6 because its not working anymore without touching the build server environment.
Hmmm… wondering if this has something to do with the long filename support. Will investigate.
I’ve not been able to reproduce this here, using hard code paths works fine, provided the exe actually exists on the agent. Did it perhaps run on a different agent that didn’t have mstest in that location?
we have only one agent. just updated to version 1.6. and the first build failed with this message. 30 minutes ago, with version 1.5, it worked.
We’re still investigating this, the error looks to be caused by the use of AlphaFS for long paths support.
Hi Christian Leh,
We are having a bit of trouble reproducing this issue locally. Would you be able to send through the settings your using on the test action that is failing. Also if any property collector values for the agent have been altered could you also include those please.
Hi Christian,
I believe we might have found the issue. If using the custom location for the MSTest executable, did the directory specified have a space before it? For example (without quotes):
" c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\mstest.exe"
If so then this would cause the error. Removing the space will get things working again. In the meantime we are looking at a fix which will resolve this issue.
sounds good. not that urgent because the property collectors work fine.