I have build that has part of it running tests with code analysis.
I have over 400 unit tests and they all run fine during the build I checked the log but for some reason I have red X for the Running tests and Test results: No test result. Code coverage results: Not Available.
And total result for the build is failed even though log says that build succeded.
Thanks a lot.
Here is part of the log.
Run has the following issue(s):
C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning : Code coverage instrumentation warning while processing file PipeBizLib.dll:
C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning : Warning VSP2013 : Instrumenting this image requires it to run as a 32-bit process. The CLR header flags have been updated to reflect this.
C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning : .
C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning : Code coverage instrumentation warning while processing file Siata.Accounting.dll:
C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning : Warning VSP2013 : Instrumenting this image requires it to run as a 32-bit process. The CLR header flags have been updated to reflect this.
C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning : .
C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning : Code coverage instrumentation warning while processing file Siata.Common.dll:
C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning : Warning VSP2013 : Instrumenting this image requires it to run as a 32-bit process. The CLR header flags have been updated to reflect this.
C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning : .
415/415 test(s) Passed
Summary
-------
Test Run Warning.
Passed 415
-----------
Total 415
Results file: C:\builds\siata\Siata\Debug HQ\TestResults\Shimon_SIATA 2006-05-10 21_03_30_Mixed Platforms_Debug HQ.trx
Run Configuration: Local Test Run
Waiting to publish...
Publishing results of test run Shimon@SIATA 2006-05-10 21:03:30_Mixed Platforms_Debug HQ to http://win03:8080/Build/v1.0/PublishTestResultsBuildService.asmx...
The drop share directory "\\siata\siata documents\siata\builds\Debug HQ_20060510.3" could not be accessed.
MSBUILD : warning : The drop share directory "\\siata\siata documents\siata\builds\Debug HQ_20060510.3" could not be accessed.
The previous error was converted to a warning because the task was called with ContinueOnError=true.
Build continuing because "ContinueOnError" on the task "TestToolsTask" is set to "true".
Done building target "RunTestWithConfiguration" in project "TFSBuild.proj".
Done building project "TFSBuild.proj".
Target CoreDropBuild:
Creating directory \\siata\siata documents\siata\builds\Debug HQ_20060510.3\Mixed Platforms\Debug HQ.
......................................................
Copying file from "C:\builds\siata\Siata\Debug HQ\BuildType\..\Sources\..\Binaries\Mixed Platforms\Debug HQ\Documents\DocumentDatabaseTests.cs" to "\\siata\siata documents\siata\builds\Debug HQ_20060510.3\Mixed Platforms\Debug HQ\Documents\DocumentDatabaseTests.cs".
Target CopyLogFiles:
Copying file from "C:\builds\siata\Siata\Debug HQ\BuildType\ErrorsWarningsLog.txt" to "\\siata\siata documents\siata\builds\Debug HQ_20060510.3\ErrorsWarningsLog.txt".
Build succeeded.
Test results: No test resutls
Mjman15
Not sure why you're running into this issue - the drop share can be on the build machine. You'll just need to make sure that the build service account (whatever account TfsBuildService.exe is running under) has full permissions on the share. (Not just NT permissions - sharing permissions. Right click on the drop root, select Sharing and Security, click Permissions on the Sharing tab)
-Aaron
TimSE
I've given full permissions to everyone in the Permissions menu in the sharing tab as well as on the security tab. All of my builds work fine except for those that perform testing after the build.
I also get the same error when I attempt to manually publish a test result from the test results window.
adi123
I am having the same problem. Zero errors, zero warnings, and build fails because the shared drop location is not accessible. When the drop location is changed to the foundation server, I get a successful build.
However, moving my drop location to the foundation server is not an acceptable solution for me. Saving a seperate folder for each set of test results with its own executable uses too much space and I would prefer to not save this information on the foundation server.
Why can't the drop location be on the build machine The documentation says that the drop location can be anywhere that is accessible over the network.
Alternatively, is there a way to set up the foundation server so that only the .trx files are stored when test results are published
Bill H123
I think the problem with the tests are in this line
The drop share directory "\\siata\builds\Debug with Tests_20060511.1" could not be accessed.
MSBUILD : warning : The drop share directory "\\siata\builds\Debug with Tests_20060511.1" could not be accessed.
I just don't understand - I gave full control for this folder to everyone so what gives !
Thanks
m4yster
OK. Issue is resolved.
Build share location must be on the server. It can't be on build machine.
WLT
I found that when publishing happens the account running the TFS is one that need perms also to the drop share. You still need the build service account to have perms as well. So we have TFS on machine A running with account1. We have build on machine B running under account2. So the share needs to have account1 (TFS account) read/write perms as well as account2 (Build Machine Service Account.)