nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

I'm guessing (hoping?) that the problem is _not_ in the middle of the
test, but when the original remoting call from JetBrains returns. If
that's so, we can simply fix it when returning from whatever they
call.

Nicholas, perhaps the full stack trace would help us decide.

Charlie

On Wed, Nov 28, 2012 at 11:48 AM, Simone Busoli
<1084181@xxxxxxxxxxxxxxxxxx> wrote:
> Yeah but where should we clear it? The remoting call happens within the
> test, our junction points are eventually before and after the test,
> certainly not during.
> On Nov 28, 2012 8:45 PM, "Charlie Poole" <charlie@xxxxxxxxx> wrote:
>
>> Where in the NUnit code is this occuring... that is, what does Resharper
>> actually call into.
>>
>> My thought is that  we could clear the context when we no longer need
>> it.
>>
>> Charlie
>>
>> --
>> You received this bug notification because you are a bug assignee.
>> https://bugs.launchpad.net/bugs/1084181
>>
>> Title:
>>   TestExecutaionContext SerializationException
>>
>> Status in NUnit V2 Test Framework:
>>   Confirmed
>>
>> Bug description:
>>   Nunit v 2.6.2.12296 throws a SerializationException  because
>>   TestExecutaionContext is not marked as Serializable.
>>
>>   Looks like TestExecutaionContext is calling
>> CallContext.LogicalSetData("Nunit.Framework.TestContext",current.contextDictionary)
>>   however contextDictionary=> TestExecutaionContext  is not Serializable.
>> This prevents remote calls. You will get a
>>   System.Runtime.Serialization.SerializationException : Type
>> 'NUnit.Core.TestExecutionContext' in Assembly 'nunit.core,
>> Version=2.6.2.12296, Culture=neutral, PublicKeyToken=96d09a1eb7f44a77' is
>> not marked as serializable
>>   exception.
>>   You can work around this by calling
>>   CallContext.FreeNamedDataSlot("NUnit.Framework.TestContext");
>>   but is ugly and might break your expectation about what is in the
>> context?
>>   -Erik
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/nunitv2/+bug/1084181/+subscriptions
>>
>
> --
> You received this bug notification because you are subscribed to NUnit
> Extended Testing Platform.
> https://bugs.launchpad.net/bugs/1084181
>
> Title:
>   TestExecutaionContext SerializationException
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunitv2/+bug/1084181/+subscriptions

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/1084181

Title:
  TestExecutaionContext SerializationException

Status in NUnit V2 Test Framework:
  Confirmed

Bug description:
  Nunit v 2.6.2.12296 throws a SerializationException  because
  TestExecutaionContext is not marked as Serializable.

  Looks like TestExecutaionContext is calling CallContext.LogicalSetData("Nunit.Framework.TestContext",current.contextDictionary)
  however contextDictionary=> TestExecutaionContext  is not Serializable. This prevents remote calls. You will get a 
  System.Runtime.Serialization.SerializationException : Type 'NUnit.Core.TestExecutionContext' in Assembly 'nunit.core, Version=2.6.2.12296, Culture=neutral, PublicKeyToken=96d09a1eb7f44a77' is not marked as serializable
  exception.
  You can work around this by calling
  CallContext.FreeNamedDataSlot("NUnit.Framework.TestContext");
  but is ugly and might break your expectation about what is in the context?
  -Erik

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/1084181/+subscriptions