Bug 53483 - MSBuild failures in XS test suite
Summary: MSBuild failures in XS test suite
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Tools
Classification: Mono
Component: msbuild ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Ankit Jain
URL:
Depends on:
Blocks:
 
Reported: 2017-03-17 18:31 UTC by Rodrigo Kumpera
Modified: 2017-03-28 17:58 UTC (History)
2 users (show)

Tags: 2017-02
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NOT_REPRODUCIBLE

Description Rodrigo Kumpera 2017-03-17 18:31:20 UTC
With the XS 2017-02 lane and this build:
https://wrench.internalx.com/Wrench/ViewLane.aspx?lane_id=4354&host_id=387&revision_id=868542

The test-UnitTests step has two msbuild failures:

1) ProjectReferencingConditionalReferences (MonoDevelop.Projects.ProjectTests.ProjectReferencingConditionalReferences)
   MonoDevelop.Core.Execution.RemoteProcessException : Not connected
  at MonoDevelop.Core.Execution.RemoteProcessConnection.PostMessage (MonoDevelop.Core.Execution.BinaryMessage message, System.Threading.Tasks.TaskCompletionSource`1[TResult] cs, System.Boolean checkInitialized) [0x000a5] in /Users/builder/data/lanes/4354/8c1e7cfc/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Core.Execution/RemoteProcessConnection.cs:353 
  at MonoDevelop.Core.Execution.RemoteProcessConnection.SendMessage (MonoDevelop.Core.Execution.BinaryMessage message) [0x00031] in /Users/builder/data/lanes/4354/8c1e7cfc/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Core.Execution/RemoteProcessConnection.cs:310 
  at MonoDevelop.Projects.MSBuild.MSBuildProjectService+<>c__DisplayClass83_1+<<GetProjectBuilder>b__0>d.MoveNext () [0x00233] in /Users/builder/data/lanes/4354/8c1e7cfc/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Projects.MSBuild/MSBuildProjectService.cs:1005 

2) BuildingAndCleaning (MonoDevelop.Projects.SolutionTests.BuildingAndCleaning)
   MonoDevelop.Core.Execution.RemoteProcessException : Not connected
  at MonoDevelop.Core.Execution.RemoteProcessConnection.PostMessage (MonoDevelop.Core.Execution.BinaryMessage message, System.Threading.Tasks.TaskCompletionSource`1[TResult] cs, System.Boolean checkInitialized) [0x000a5] in /Users/builder/data/lanes/4354/8c1e7cfc/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Core.Execution/RemoteProcessConnection.cs:353 
  at MonoDevelop.Core.Execution.RemoteProcessConnection.SendMessage (MonoDevelop.Core.Execution.BinaryMessage message) [0x00031] in /Users/builder/data/lanes/4354/8c1e7cfc/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Core.Execution/RemoteProcessConnection.cs:310 
  at MonoDevelop.Projects.MSBuild.MSBuildProjectService+<>c__DisplayClass83_1+<<GetProjectBuilder>b__0>d.MoveNext () [0x00233] in /Users/builder/data/lanes/4354/8c1e7cfc/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Projects.MSBuild/MSBuildProjectService.cs:1005
Comment 1 Ankit Jain 2017-03-21 20:51:22 UTC
I can't reproduce this. It works for me. Could you please check again if it is still an issue?
Comment 2 Ankit Jain 2017-03-28 17:58:27 UTC
XS-mdaddins/master is being built with mono 2017-02 now (mono 4.9.3.54 to be exact) on wrench and these tests are not failing with that. Closing the issue.