System.NullReferenceException 2.6.0.11089

Bug #816863 reported by André Verwijs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnit V2
Fix Released
High
Jordan Terrell

Bug Description

tested today, got this when loaded a .sln solution... maybe this is allready fixed, but still want to report it...

System.NullReferenceException...

Server stack trace:
   bij NUnit.Core.ActionsHelper.GetActionsFromAttributes(ICustomAttributeProvider attributeProvider)
   bij NUnit.Core.TestAssembly..ctor(Assembly assembly, String path)
   bij NUnit.Core.Builders.TestAssemblyBuilder.BuildTestAssembly(Assembly assembly, String assemblyName, IList fixtures, Boolean autoSuites)
   bij NUnit.Core.Builders.TestAssemblyBuilder.Build(String assemblyName, Boolean autoSuites)
   bij NUnit.Core.Builders.TestAssemblyBuilder.Build(String assemblyName, String testName, Boolean autoSuites)
   bij NUnit.Core.TestSuiteBuilder.Build(TestPackage package)
   bij NUnit.Core.SimpleTestRunner.Load(TestPackage package)
   bij NUnit.Core.ProxyTestRunner.Load(TestPackage package)
   bij NUnit.Core.ProxyTestRunner.Load(TestPackage package)
   bij NUnit.Core.RemoteTestRunner.Load(TestPackage package)
   bij System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   bij System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   bij System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
   bij System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   bij System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   bij NUnit.Core.TestRunner.Load(TestPackage package)
   bij NUnit.Util.TestDomain.Load(TestPackage package)
   bij NUnit.Util.TestLoader.LoadTest(String testName)

 thanks

Revision history for this message
Charlie Poole (charlie.poole) wrote :

We suspect this may be caused by running a test that was built against an older (than 2.6 ) version of NUnit. Can you tell us whether that's the case for you?

tags: removed: 2.6.0.11089 nunit
Revision history for this message
Charlie Poole (charlie.poole) wrote :

This appears to be fixed in NUnit 2.6.0.11240.

Changed in nunitv2:
importance: Undecided → High
assignee: nobody → Jordan Terrell (jterrell)
milestone: none → 2.6.0b1
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.