34 references to Trace
Microsoft.Build (34)
BackEnd\Client\MSBuildClient.cs (13)
172CommunicationsUtilities.Trace("Executing build with command line '{0}'", descriptiveCommandLine); 210CommunicationsUtilities.Trace("Failed to obtain the current build server state: {0}", ex); 211CommunicationsUtilities.Trace("HResult: {0}.", ex.HResult); 369CommunicationsUtilities.Trace("MSBuild client error: problem during packet handling occurred: {0}.", ex); 394CommunicationsUtilities.Trace("MSBuild client warning: problem during querying console buffer width.", ex); 427CommunicationsUtilities.Trace("Command packet of type '{0}' sent...", packet.Type); 462CommunicationsUtilities.Trace("Failed to obtain the current build server state: {0}", ex); 463CommunicationsUtilities.Trace("HResult: {0}.", ex.HResult); 478CommunicationsUtilities.Trace("Server started with PID: {0}", msbuildProcess?.Id); 482CommunicationsUtilities.Trace("Failed to launch the msbuild server: {0}", ex); 559CommunicationsUtilities.Trace("MSBuild client error: packet pump unexpectedly shut down: {0}", packetPump.PacketPumpException); 630CommunicationsUtilities.Trace("Retrying to connect to server after {0} ms", sw.ElapsedMilliseconds); 638CommunicationsUtilities.Trace("Failed to connect to server: {0}", ex);
BackEnd\Client\MSBuildClientPacketPump.cs (2)
283CommunicationsUtilities.Trace("Packet factory failed to receive package. Exception while deserializing packet {0}.", packetType); 312CommunicationsUtilities.Trace("Exception occurred in the packet pump: {0}", ex);
BackEnd\Components\Communications\DetouredNodeLauncher.cs (1)
74CommunicationsUtilities.Trace("Launching node from {0}", msbuildLocation);
BackEnd\Components\Communications\NodeLauncher.cs (1)
92CommunicationsUtilities.Trace("Launching node from {0}", msbuildLocation);
BackEnd\Components\Communications\NodeProviderOutOfProcBase.cs (7)
175CommunicationsUtilities.Trace("Shutting down node with pid = {0}", nodeProcess.Id); 366CommunicationsUtilities.Trace("Could not connect to node with PID {0}; it has exited with unknown exit code. This can indicate a crash at startup", msbuildProcess.Id); 372CommunicationsUtilities.Trace("Could not connect to node with PID {0}; it is still running. This can occur when two multiprocess builds run in parallel and the other one 'stole' this node", msbuildProcess.Id); 515CommunicationsUtilities.Trace("Reading handshake from pipe {0}", pipeName); 523CommunicationsUtilities.Trace("Successfully connected to pipe {0}...!", pipeName); 839CommunicationsUtilities.Trace("Waiting for node with pid = {0} to exit", _process.Id); 867CommunicationsUtilities.Trace("Killing node with pid = {0}", _process.Id);
BackEnd\Node\OutOfProcNode.cs (1)
488CommunicationsUtilities.Trace("Failed to restore the original environment: {0}.", ex);
BackEnd\Node\OutOfProcServerNode.cs (2)
110CommunicationsUtilities.Trace("Starting new server node with handshake {0}", handshake); 349CommunicationsUtilities.Trace("Building with MSBuild server with command line {0}", command.CommandLine);
CommunicationsUtilities.cs (2)
492CommunicationsUtilities.Trace("Handshake failed on part {0}. Probably the client is a different MSBuild build.", valueRead); 496CommunicationsUtilities.Trace("Expected end of handshake signal but received {0}. Probably the host is a different MSBuild build.", valueRead);
NodeEndpointOutOfProcBase.cs (5)
372CommunicationsUtilities.Trace("Waiting for connection {0} ms...", waitTimeRemaining); 453CommunicationsUtilities.Trace("Client connection failed but we will wait for another connection. Exception: {0}", e.Message); 475CommunicationsUtilities.Trace("Client connection failed. Exiting comm thread. {0}", e); 561CommunicationsUtilities.Trace("Exception reading from server. {0}", e); 654CommunicationsUtilities.Trace("Exception while serializing packets: {0}", e);