Databases
StackOverflow2013
Postsdbo
POTeamCity - MSBuild runner exits with not zero code
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POTeamCity - MSBuild runner exits with not zero code
    primarykey
    data
    text
    <p>I've had TeamCity running for a long time, with no problems.</p> <p>I then upgraded to TeamCity 8, and now all my .Net projects fail when launching the Test build step.</p> <p>The only error message I see is this: <code>MSBuild runner exits with not zero code</code></p> <p>The test part of my log, looks like this:</p> <pre><code>[10:39:08][Step 1/2] Process exited with code 0 [10:39:08]Step 2/2: Test (MSTest) (20s) [10:39:08][Step 2/2] Starting: F:\TeamCity\buildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher.exe #TeamCityImplicit [10:39:08][Step 2/2] in directory: F:\TeamCity\buildAgent\work\382c54c35fd97a3e [10:39:13][Step 2/2] JetBrains dotCover Console Runner v2.2.515.44. Copyright (c) 2009-2013 JetBrains s.r.o. All rights reserved. [10:39:13][Step 2/2] [10:39:28][Step 2/2] [JetBrains dotCover] Coverage session started [6/29/2013 10:39:28 AM] [10:39:28][Step 2/2] [JetBrains dotCover] Coverage session finished with errors: Can't initialize profiler. [10:39:28][Step 2/2] [10:39:28][Step 2/2] Product installation directory has no read access rights for WinRT applications.. [10:39:28][Step 2/2] ##teamcity[importData type='dotNetCoverage' tool='dotcover' file='F:\TeamCity\buildAgent\temp\buildTmp\coverage_dotcover79745141367270310401.data'] [10:39:29][Step 2/2] Importing data from 'F:\TeamCity\buildAgent\temp\buildTmp\coverage_dotcover79745141367270310401.data' (not existing file) with 'dotNetCoverage' processor [10:39:29][Step 2/2] Rejected coverage report file: F:\TeamCity\buildAgent\temp\buildTmp\coverage_dotcover79745141367270310401.data size: 0. File is empty or does not exist [10:39:29][Step 2/2] Process exited with code -2 [10:39:29][Step 2/2] Step Test (MSTest) failed [10:39:29]Waiting for 1 service processes to complete [10:39:29]Publishing internal artifacts [10:39:29][Publishing internal artifacts] Sending build.finish.properties.gz file [10:39:29]Build finished </code></pre> <p>If I look at the <code>teamcity-build.log</code> file, I can see it says err on the line where the <code>NUitLauncher</code> is executed:</p> <pre><code>[2013-06-29 10:39:08,134] out - [2013-06-29 10:39:08,134] out - 14 Warning(s) [2013-06-29 10:39:08,134] out - 0 Error(s) [2013-06-29 10:39:08,134] out - [2013-06-29 10:39:08,134] out - Time Elapsed 00:00:19.87 [2013-06-29 10:39:08,485] out - Process exited with code 0 [2013-06-29 10:39:08,736] out - ----------------------------------------- [ Backstage::Build and Test #62 (buildId = 874) ] ----------------------------------------- [2013-06-29 10:39:08,739] out - Starting: F:\TeamCity\buildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher.exe #TeamCityImplicit [2013-06-29 10:39:08,739] out - in directory: F:\TeamCity\buildAgent\work\382c54c35fd97a3e [2013-06-29 10:39:08,746] err - F:\TeamCity\buildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher.exe #TeamCityImplicit [2013-06-29 10:39:13,336] out - JetBrains dotCover Console Runner v2.2.515.44. Copyright (c) 2009-2013 JetBrains s.r.o. All rights reserved. [2013-06-29 10:39:13,336] out - JetBrains dotCover Console Runner v2.2.515.44. Copyright (c) 2009-2013 JetBrains s.r.o. All rights reserved. [2013-06-29 10:39:13,336] out - [2013-06-29 10:39:13,337] out - [2013-06-29 10:39:28,002] out - [JetBrains dotCover] Coverage session started [6/29/2013 10:39:28 AM] [2013-06-29 10:39:28,002] out - [JetBrains dotCover] Coverage session started [6/29/2013 10:39:28 AM] [2013-06-29 10:39:28,752] out - [JetBrains dotCover] Coverage session finished with errors: Can't initialize profiler. [2013-06-29 10:39:28,753] out - [JetBrains dotCover] Coverage session finished with errors: Can't initialize profiler. [2013-06-29 10:39:28,753] out - [2013-06-29 10:39:28,753] out - [2013-06-29 10:39:28,753] out - Product installation directory has no read access rights for WinRT applications.. [2013-06-29 10:39:28,753] out - Product installation directory has no read access rights for WinRT applications.. [2013-06-29 10:39:29,170] out - Process exited with code -2 </code></pre> <p>Anyone else seen this? Is there a place to find more extensive log information?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMartinHN
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POTeamCity - MSBuild runner exits with not zero code
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POTeamCity - MSBuild runner exits with not zero code
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POTeamCity - MSBuild runner exits with not zero code
      1. USjrummell
      1. VTFavorite
    1. COI had a very similar issue, and following the instructions here fixed it: http://confluence.jetbrains.com/pages/viewpage.action?pageId=49448495
      singulars
      1. POTeamCity - MSBuild runner exits with not zero code
      1. USjrummell
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload