Just started getting this on multiple machines trying to execute tests via the Resharper Test Runner while collecting coverage via dotcover. Profiling is enabled and dotcover is selected as an additional profiler. This configuration has been working for a while, its a very large solution with 100's of devs so its very possible a version changed etc. Just looking for some direction on where to start looking.
At the same time of the errors I see the following two entries in the System Event Log.
.NET Runtime version 4.0.30319.0 - The profiler was loaded successfully. Profiler CLSID: '{b7abe522-a68f-44f2-925b-81e7488e9ec0}'. Process ID (decimal): 180616. Message ID: [0x2507].
.NET Runtime version 2.0.50727.5485 - Failed to CoCreate profiler.
System.Runtime.Serialization.SerializationException
Type 'Telerik.JustMock.Core.Behaviors.EventStubsBehavior+EventsMixin' in Assembly 'Telerik.JustMock, Version=2016.1.307.3, Culture=neutral, PublicKeyToken=721b6c5bc0326b3a' is not marked as serializable.
Server stack trace:
at System.Runtime.Serialization.FormatterServices.InternalGetSerializableMembers(RuntimeType type)
at System.Runtime.Serialization.FormatterServices.GetSerializableMembers(Type type, StreamingContext context)
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitMemberInfo()
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter, SerializationBinder binder)
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter, SerializationBinder binder)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write(WriteObjectInfo objectInfo, NameInfo memberNameInfo, NameInfo typeNameInfo)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck)
at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.SerializeMessageParts(ArrayList argsToSerialize)
at System.Runtime.Remoting.Messaging.SmuggledMethodCallMessage..ctor(IMethodCallMessage mcm)
at System.Runtime.Remoting.Messaging.SmuggledMethodCallMessage.SmuggleIfPossible(IMessage msg)
at System.Runtime.Remoting.Channels.CrossAppDomainSink.SyncProcessMessage(IMessage reqMsg)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Xunit.Abstractions.IMessageSink.OnMessage(IMessageSinkMessage message)
at Xunit.Sdk.SynchronousMessageBus.QueueMessage(IMessageSinkMessage message) in C:\BuildAgent\work\cb37e9acf085d108\src\xunit.execution\Sdk\SynchronousMessageBus.cs:line 24
at ReflectionAbstractionExtensions.CreateTestClass(ITest test, Type testClassType, Object[] constructorArguments, IMessageBus messageBus, ExecutionTimer timer, CancellationTokenSource cancellationTokenSource) in C:\BuildAgent\work\cb37e9acf085d108\src\xunit.execution\Extensions\ReflectionAbstractionExtensions.cs:line 45
at Xunit.Sdk.TestInvoker`1.CreateTestClass() in C:\BuildAgent\work\cb37e9acf085d108\src\xunit.execution\Sdk\Frameworks\Runners\TestInvoker.cs:line 121
at Xunit.Sdk.TestInvoker`1.<<RunAsync>b__45_0>d.MoveNext() in C:\BuildAgent\work\cb37e9acf085d108\src\xunit.execution\Sdk\Frameworks\Runners\TestInvoker.cs:line 160
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Xunit.Sdk.ExceptionAggregator.<RunAsync>d__10`1.MoveNext() in C:\BuildAgent\work\cb37e9acf085d108\src\xunit.core\Sdk\ExceptionAggregator.cs:line 107
8 Answers, 1 is accepted
Thank you for your feedback.
That is a known issue that we will address in the next internal build so please, stay tuned.
Regards,
Svetlozar
Telerik by Progress
Rank 1
No, that fix didn't make it for the official release. It will be available in the next internal build.
I am really sorry for the inconvenience!
Regards,
Svetlozar
Telerik by Progress
Rank 1
Unfortunately a fix for this issue is not yet released neither in official or internal build. The reason behind this is that it turned out to be more complex then our initial expectations.
That's why we would ask you to send us a simple application in which you reproduce it as it may happen in different scenarios and we want to be sure that we are covering more cases. Also it is important to give us an information about the specifics of the setup of your server where you execute the tests.
Regards,
Kamen Ivanov
Telerik by Progress
Rank 1
Hi,
I have the same problem executing the latest version of JetBrains dotCover 2016.3.2 with JustMock 2016.3.914.2. I can not calculate the coverage because the process doesn't finish. JetBrains says that it is a JustMock integration.
Do you have some feedback about this issue?
This is a known issue.
Unfortunately JetBrains have changed their behavior in version 2016.2 of dotCover and since then the integration is not working.
You could still use dotCover 2016.1.2 or earlier version and the code coverage will finish and will show results.
We have logged an issue in our backlog regarding this but it will not be fixed in the upcoming release in the beginning of May.
Regards,
Kamen Ivanov
Telerik by Progress
Rank 1
Hi Kamen,
I'm profiler architect from JetBrains. I don't remember that we had changed something important in the profiler between 2016.1.2 and 2016.2. There were only some bugs. Could you please contact to me directly with technical details ( mikhail [dоt] pilin [аt] jetbrains [dоt] com) ?
With best wishes,
Mikhail Pilin