NUnit V2

x86 Console crash

Asked by Dunken

Hi

I'm using nunit 2.5.8 (x86) on a 64bit system. As long as I'm using the GUI runner everything works as expected. However, if I start using the Console runner (nunit-console-x86.exe) I run into an unhandled exception (console crashes):

Any hints?

Thank you.
Regards,

Description:
  Stopped working

Problem signature:
  Problem Event Name: CLR20r3
  Problem Signature 01: nunit-console-x86.exe
  Problem Signature 02: 2.5.8.10295
  Problem Signature 03: 4cc21695
  Problem Signature 04: mscorlib
  Problem Signature 05: 2.0.0.0
  Problem Signature 06: 4ef6c7cc
  Problem Signature 07: 3452
  Problem Signature 08: 26d
  Problem Signature 09: System.IO.IOException
  OS Version: 6.1.7601.2.1.0.256.1
  Locale ID: 2055

Question information

Language:
English Edit question
Status:
Open
For:
NUnit V2 Edit question
Assignee:
Charlie Poole Edit question
Last query:
Last reply:
Revision history for this message
Charlie Poole (charlie.poole) said : 		#1

Clearly it's some sort of IO error. Can you provide a stack trace?

Revision history for this message
Dunken (mc-ghc) said : 		#2

Hi Charlie

Yes, here's the stack trace:

>    mscorlib.dll!System.IO.__Error.WinIOError(int errorCode = 6, string maybeFullPath = "") + 0x498 bytes
     mscorlib.dll!System.IO.__ConsoleStream.Write(byte[] buffer, int offset, int count) + 0x15e bytes
     mscorlib.dll!System.IO.StreamWriter.Flush(bool flushStream, bool flushEncoder) + 0x60 bytes
     mscorlib.dll!System.IO.StreamWriter.Write(char[] buffer = {char[574]}, int index = 256, int count = 318) + 0xa2 bytes
     mscorlib.dll!System.IO.TextWriter.WriteLine(string value) + 0xa1 bytes
     mscorlib.dll!System.IO.TextWriter.WriteLine(string format, object arg0) + 0x49 bytes
     mscorlib.dll!System.IO.TextWriter.SyncTextWriter.WriteLine(string format, object arg0) + 0x22 bytes
     mscorlib.dll!System.Console.WriteLine(string format, object arg0) + 0x1b bytes
     nunit-console-runner.dll!NUnit.ConsoleRunner.Runner.Main(string[] args) + 0x414 bytes
     nunit-console-x86.exe!NUnit.ConsoleRunner.Class1.Main(string[] args) + 0x6 bytes

Regards,

________________________________
 Von: Charlie Poole <email address hidden>
An: <email address hidden>
Gesendet: 22:45 Montag, 16.Juli 2012
Betreff: Re: [Question #203311]: x86 Console crash

Your question #203311 on NUnit V2 changed:
https://answers.launchpad.net/nunitv2/+question/203311

    Status: Open => Needs information

Charlie Poole requested more information:
Clearly it's some sort of IO error. Can you provide a stack trace?

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/nunitv2/+question/203311

You received this question notification because you asked the question.

Revision history for this message
Dunken (mc-ghc) said : 		#3

Hi Charlie

It seems like it's because I called Console.WriteLine() in one of my tests. Am I not supposed to use it?

Regards,

________________________________
 Von: Galliker Armin <email address hidden>
An: "<email address hidden>" <email address hidden>
Gesendet: 8:20 Dienstag, 17.Juli 2012
Betreff: Re: [Question #203311]: x86 Console crash

Hi Charlie

Yes, here's the stack trace:

>    mscorlib.dll!System.IO.__Error.WinIOError(int errorCode = 6, string maybeFullPath = "") + 0x498 bytes
     mscorlib.dll!System.IO.__ConsoleStream.Write(byte[] buffer, int offset, int count) + 0x15e bytes
     mscorlib.dll!System.IO.StreamWriter.Flush(bool flushStream, bool flushEncoder) + 0x60 bytes
     mscorlib.dll!System.IO.StreamWriter.Write(char[] buffer = {char[574]}, int index = 256, int count = 318) + 0xa2 bytes
     mscorlib.dll!System.IO.TextWriter.WriteLine(string value) + 0xa1
 bytes
     mscorlib.dll!System.IO.TextWriter.WriteLine(string format, object arg0) + 0x49 bytes
     mscorlib.dll!System.IO.TextWriter.SyncTextWriter.WriteLine(string format, object arg0) + 0x22 bytes
     mscorlib.dll!System.Console.WriteLine(string format, object arg0) + 0x1b bytes
     nunit-console-runner.dll!NUnit.ConsoleRunner.Runner.Main(string[] args) + 0x414 bytes
     nunit-console-x86.exe!NUnit.ConsoleRunner.Class1.Main(string[] args) + 0x6 bytes

Regards,

________________________________
 Von: Charlie Poole <email address hidden>
An: <email address hidden>
Gesendet: 22:45 Montag, 16.Juli 2012
Betreff: Re: [Question #203311]: x86 Console crash

Your question #203311 on NUnit V2 changed:
https://answers.launchpad.net/nunitv2/+question/203311

    Status: Open => Needs information

Charlie Poole requested more information:
Clearly it's some sort of IO error. Can you provide a stack trace?

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/nunitv2/+question/203311

You received this question notification because you asked the question.

Revision history for this message
Charlie Poole (charlie.poole) said : 		#4

You should be able to do that, but of course bugs happen.

The exception occured when nunit-console's Main was writing to the console.
This would have to be either before or after all your tests were run. Can you
determine which is the case? If after, then it's possible that your own console
write is causing the issue. What happens if you remove it?

Charlie

On Wed, Jul 18, 2012 at 4:15 AM, Dunken
<email address hidden> wrote:
> Question #203311 on NUnit V2 changed:
> https://answers.launchpad.net/nunitv2/+question/203311
>
> Dunken gave more information on the question:
> Hi Charlie
>
> It seems like it's because I called Console.WriteLine() in one of my
> tests. Am I not supposed to use it?
>
> Regards,
>
>
> ________________________________
> Von: Galliker Armin <email address hidden>
> An: "<email address hidden>" <email address hidden>
> Gesendet: 8:20 Dienstag, 17.Juli 2012
> Betreff: Re: [Question #203311]: x86 Console crash
>
>
> Hi Charlie
>
> Yes, here's the stack trace:
>
>> mscorlib.dll!System.IO.__Error.WinIOError(int errorCode = 6, string maybeFullPath = "") + 0x498 bytes
> mscorlib.dll!System.IO.__ConsoleStream.Write(byte[] buffer, int offset, int count) + 0x15e bytes
> mscorlib.dll!System.IO.StreamWriter.Flush(bool flushStream, bool flushEncoder) + 0x60 bytes
> mscorlib.dll!System.IO.StreamWriter.Write(char[] buffer = {char[574]}, int index = 256, int count = 318) + 0xa2 bytes
> mscorlib.dll!System.IO.TextWriter.WriteLine(string value) + 0xa1
> bytes
> mscorlib.dll!System.IO.TextWriter.WriteLine(string format, object arg0) + 0x49 bytes
> mscorlib.dll!System.IO.TextWriter.SyncTextWriter.WriteLine(string format, object arg0) + 0x22 bytes
> mscorlib.dll!System.Console.WriteLine(string format, object arg0) + 0x1b bytes
> nunit-console-runner.dll!NUnit.ConsoleRunner.Runner.Main(string[] args) + 0x414 bytes
> nunit-console-x86.exe!NUnit.ConsoleRunner.Class1.Main(string[] args) + 0x6 bytes
>
>
> Regards,
>
>
> ________________________________
> Von: Charlie Poole <email address hidden>
> An: <email address hidden>
> Gesendet: 22:45 Montag, 16.Juli 2012
> Betreff: Re: [Question #203311]: x86 Console crash
>
> Your question #203311 on NUnit V2 changed:
> https://answers.launchpad.net/nunitv2/+question/203311
>
> Status: Open => Needs information
>
> Charlie Poole requested more information:
> Clearly it's some sort of IO error. Can you provide a stack trace?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/nunitv2/+question/203311
>
> You received this question notification because you asked the question.
>
> You received this question notification because you are an answer
> contact for NUnit V2.

Revision history for this message
Dunken (mc-ghc) said : 		#5

Even removing all Console.WriteLine() didn't solve the issue. Maybe it's something else. Here are the logs:

nunit-console_3872.log:

InternalTrace: Initializing at level Verbose
09:56:41.855 Info  [ 1] Runner: NUnit-console.exe starting
09:56:41.874 Debug [ 1] ServiceManager: Added SettingsService
09:56:41.874 Debug [ 1] ServiceManager: Added DomainManager
09:56:41.875 Debug [ 1] ServiceManager: Added ProjectService
09:56:41.875 Debug [ 1] ServiceManager: Added AddinRegistry
09:56:41.876 Debug [ 1] ServiceManager: Added AddinManager
09:56:41.877 Debug [ 1] ServiceManager: Added TestAgency
09:56:41.877 Info  [ 1] ServiceManager: Initializing SettingsService
09:56:41.877 Info  [ 1] ServiceManager: Initializing DomainManager
09:56:41.877 Info  [ 1] ServiceManager: Initializing ProjectService
09:56:41.878 Info  [ 1] ServiceManager: Initializing AddinRegistry
09:56:41.878 Info  [ 1] ServiceManager: Initializing AddinManager
09:56:41.879 Debug [ 1] ServiceManager: Request for service IAddinRegistry satisfied by AddinRegistry
09:56:41.881 Info  [ 1] ServiceManager: Initializing TestAgency
09:56:41.904 Debug [ 1] ServiceManager: Request for service ProjectService satisfied by ProjectService
09:56:41.921 Debug [ 1] RuntimeFrameworkSelector: Current framework is net-2.0
09:56:41.921 Debug [ 1] RuntimeFrameworkSelector: No specific framework requested
09:56:41.923 Debug [ 1] RuntimeFrameworkSelector: Assembly c:\tests\Bin\MyTest.dll uses version 2.0.50727
09:56:41.930 Debug [ 1] RuntimeFrameworkSelector: Preferred version 2.0.50727 is not installed or this NUnit installation does not support it
09:56:41.930 Debug [ 1] RuntimeFrameworkSelector: Test will use net-2.0.50727 framework
09:56:41.932 Info  [ 1] TestDomain: Loading MyTest.dll
09:56:41.932 Debug [ 1] ServiceManager: Request for service DomainManager satisfied by DomainManager
09:56:41.935 Debug [ 1] ServiceManager: Request for service ISettings satisfied by SettingsService
09:56:41.936 Info  [ 1] DomainManager: Creating AppDomain test-domain-MyTest.dll
09:56:42.152 Info  [ 1] TestDomain: Loading tests in AppDomain, see test-domain-MyTest.dll.log
09:56:48.701 Info  [ 1] TestDomain: Unloading
09:56:48.702 Info  [ 1] TestDomain: Stopping DomainAgent
09:56:48.702 Info  [ 1] TestDomain: Unloading AppDomain test-domain-MyTest.dll
09:56:48.703 Info  [ 1] DomainManager: Unloading AppDomain test-domain-MyTest.dll
09:56:50.389 Info  [ 1] Runner: NUnit-console.exe terminating

test-domain-MyTest.dll_3872.log:

InternalTrace: Initializing at level Verbose
09:56:42.124 Info  [ 1] DomainInitializer: Initializing domain test-domain-MyTest.dll
09:56:42.124 Debug [ 1] DomainInitializer:   Base Directory: c:\Test\Bin
09:56:42.124 Debug [ 1] DomainInitializer:   Probing Path:
09:56:42.150 Info  [ 1] DomainAgent: Starting
09:56:42.151 Info  [ 1] DomainAgent: Creating RemoteTestRunner
09:56:42.162 Info  [ 1] RemoteTestRunner: Loading Test Package MyTest.dll
09:56:42.168 Info  [ 1] CoreExtensions: Installing Builtins
09:56:42.171 Info  [ 1] CoreExtensions: Installing Addins
09:56:42.174 Debug [ 1] SimpleTestRunner: Loading package MyTest.dll
09:56:42.331 Info  [ 1] TestAssemblyBuilder: Loaded assembly MyTest, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
09:56:42.332 Debug [ 1] TestAssemblyBuilder: Examining assembly for test fixtures
09:56:42.332 Debug [ 1] TestAssemblyBuilder: Found 12 classes to examine
09:56:42.395 Debug [ 1] TestAssemblyBuilder: Found 7 fixtures in 00:00:00.0615885 seconds
09:56:42.400 Info  [ 1] RemoteTestRunner: Loaded package successfully
09:56:42.432 Debug [ 1] RemoteTestRunner: Run
09:56:42.481 Debug [ 1] AssemblyResolver: Not a strong name: log4net
09:56:42.482 Info  [ 1] ThreadedTestRunner: BeginRun
09:56:42.484 Info  [ 1] ThreadedTestRunner: EndRun
09:56:42.484 Debug [ 7] SimpleTestRunner: Starting test run
09:56:47.246 Debug [ 7] TestMethod: Test Starting: MyTest.PvssDao_Test.TestCreateDataPoint
09:56:47.256 Error [ 6] EventPump: Exception in pump thread
System.IO.IOException: The handle is invalid.

Server stack trace:
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.__ConsoleStream.Write(Byte[] buffer, Int32 offset, Int32 count)
   at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   at System.IO.StreamWriter.Write(String value)
   at System.IO.TextWriter.SyncTextWriter.Write(String value)
   at NUnit.ConsoleRunner.EventCollector.TestStarted(TestName testName)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

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 NUnit.Core.EventListener.TestStarted(TestName testName)
   at NUnit.Core.TestStartedEvent.Send(EventListener listener)
   at NUnit.Core.EventPump.PumpThreadProc()
09:56:47.488 Debug [ 7] TestMethod: Test result = Success
09:56:47.490 Debug [ 7] TestMethod: Test result = Success
09:56:47.490 Debug [ 7] TestSuite: Test result = Success
09:56:47.491 Debug [ 7] TestSuite: Suite result = Success
09:56:47.491 Debug [ 7] TestMethod: Test Starting: MyTest.PvssDao_Test.TestDataAccessManager
09:56:47.492 Debug [ 7] TestMethod: Test result = Success
09:56:47.492 Debug [ 7] TestMethod: Test result = Success
09:56:47.492 Debug [ 7] TestSuite: Test result = Success
09:56:47.492 Debug [ 7] TestSuite: Suite result = Success
09:56:47.492 Debug [ 7] TestMethod: Test Starting: MyTest.PvssDao_Test.TestDeleteDataPointUsingDpId
09:56:47.544 Debug [ 7] TestMethod: Test result = Success
09:56:47.544 Debug [ 7] TestMethod: Test result = Success
09:56:47.544 Debug [ 7] TestSuite: Test result = Success
09:56:47.544 Debug [ 7] TestSuite: Suite result = Success
09:56:47.544 Debug [ 7] TestMethod: Test Starting: MyTest.PvssDao_Test.TestDeleteDataPointUsingObject
09:56:47.592 Debug [ 7] TestMethod: Test result = Success
09:56:47.592 Debug [ 7] TestMethod: Test result = Success
09:56:47.592 Debug [ 7] TestSuite: Test result = Success
09:56:47.592 Debug [ 7] TestSuite: Suite result = Success
09:56:47.592 Debug [ 7] TestMethod: Test Starting: MyTest.PvssDao_Test.TestOverloadedConstructors
09:56:47.640 Debug [ 7] TestMethod: Test result = Success
09:56:47.640 Debug [ 7] TestMethod: Test result = Success
09:56:47.640 Debug [ 7] TestSuite: Test result = Success
09:56:47.640 Debug [ 7] TestSuite: Suite result = Success
09:56:47.640 Debug [ 7] TestMethod: Test Starting: MyTest.PvssDao_Test.TestReadByQuery1
09:56:48.199 Debug [ 7] TestMethod: Test result = Success
09:56:48.200 Debug [ 7] TestMethod: Test result = Success
09:56:48.200 Debug [ 7] TestSuite: Test result = Success
09:56:48.200 Debug [ 7] TestSuite: Suite result = Success
09:56:48.200 Debug [ 7] TestMethod: Test Starting: MyTest.PvssDao_Test.TestReadByQuery2
09:56:48.283 Debug [ 7] TestMethod: Test result = Success
09:56:48.283 Debug [ 7] TestMethod: Test result = Success
09:56:48.283 Debug [ 7] TestSuite: Test result = Success
09:56:48.283 Debug [ 7] TestSuite: Suite result = Success
09:56:48.283 Debug [ 7] TestMethod: Test Starting: MyTest.PvssDao_Test.TestReadDataPoint
09:56:48.329 Debug [ 7] TestMethod: Test result = Success
09:56:48.329 Debug [ 7] TestMethod: Test result = Success
09:56:48.329 Debug [ 7] TestSuite: Test result = Success
09:56:48.329 Debug [ 7] TestSuite: Suite result = Success
09:56:48.329 Debug [ 7] TestMethod: Test Starting: MyTest.PvssDao_Test.TestReadDataPointusingDpIdentifier
09:56:48.379 Debug [ 7] TestMethod: Test result = Success
09:56:48.379 Debug [ 7] TestMethod: Test result = Success
09:56:48.379 Debug [ 7] TestSuite: Test result = Success
09:56:48.380 Debug [ 7] TestSuite: Suite result = Success
09:56:48.380 Debug [ 7] TestMethod: Test Starting: MyTest.PvssDao_Test.TestReadNonExistDataPoint
09:56:48.388 Debug [ 7] TestMethod: Test result = Success
09:56:48.388 Debug [ 7] TestMethod: Test result = Success
09:56:48.388 Debug [ 7] TestSuite: Test result = Success
09:56:48.388 Debug [ 7] TestSuite: Suite result = Success
09:56:48.388 Debug [ 7] TestMethod: Test Starting: MyTest.PvssDao_Test.TestRefreshDataPoint
09:56:48.440 Debug [ 7] TestMethod: Test result = Success
09:56:48.440 Debug [ 7] TestMethod: Test result = Success
09:56:48.440 Debug [ 7] TestSuite: Test result = Success
09:56:48.440 Debug [ 7] TestSuite: Suite result = Success
09:56:48.440 Debug [ 7] TestMethod: Test Starting: MyTest.PvssDao_Test.TestSubscriptionDataPoint
09:56:48.601 Debug [ 7] TestMethod: Test result = Success
09:56:48.601 Debug [ 7] TestMethod: Test result = Success
09:56:48.601 Debug [ 7] TestSuite: Test result = Success
09:56:48.601 Debug [ 7] TestSuite: Suite result = Success
09:56:48.601 Debug [ 7] TestMethod: Test Starting: MyTest.PvssDao_Test.TestUpdateDataPoint
09:56:48.663 Debug [ 7] TestMethod: Test result = Success
09:56:48.663 Debug [ 7] TestMethod: Test result = Success
09:56:48.663 Debug [ 7] TestSuite: Test result = Success
09:56:48.663 Debug [ 7] TestSuite: Suite result = Success
09:56:48.696 Debug [ 7] TestSuite: Test result = Success
09:56:48.696 Debug [ 7] TestSuite: Suite result = Success
09:56:48.696 Debug [ 7] TestSuite: Test result = Success
09:56:48.696 Debug [ 7] TestSuite: Suite result = Success
09:56:48.696 Debug [ 7] TestSuite: Test result = Success
09:56:48.696 Debug [ 7] TestSuite: Suite result = Success
09:56:48.696 Debug [ 7] TestSuite: Test result = Success
09:56:48.696 Debug [ 7] TestSuite: Suite result = Success
09:56:48.696 Debug [ 7] TestSuite: Test result = Success
09:56:48.696 Debug [ 7] TestSuite: Suite result = Success
09:56:48.696 Debug [ 7] TestSuite: Test result = Success
09:56:48.696 Debug [ 7] TestSuite: Suite result = Success
09:56:48.696 Debug [ 7] TestSuite: Test result = Success
09:56:48.696 Debug [ 7] TestSuite: Suite result = Success
09:56:48.696 Debug [ 7] SimpleTestRunner: Test run complete
09:56:48.702 Info  [ 1] RemoteTestRunner: Unloading test package
09:56:48.702 Debug [ 1] SimpleTestRunner: Unloading
09:56:48.702 Info  [ 1] DomainAgent: Stopping
09:56:48.715 Info  [ 2] DomainInitializer: Unloading domain test-domain-MyTest.dll

And here's how I start my test:

nunit-console-x86.exe C:\Tests\Bin\MyTest.dll /run=MyTest.PvssDao_Test

________________________________
 Von: Charlie Poole <email address hidden>
An: <email address hidden>
Gesendet: 17:11 Mittwoch, 18.Juli 2012
Betreff: Re: [Question #203311]: x86 Console crash

Your question #203311 on NUnit V2 changed:
https://answers.launchpad.net/nunitv2/+question/203311

    Status: Open => Answered

Charlie Poole proposed the following answer:
You should be able to do that, but of course bugs happen.

The exception occured when nunit-console's Main was writing to the console.
This would have to be either before or after all your tests were run. Can you
determine which is the case? If after, then it's possible that your own console
write is causing the issue. What happens if you remove it?

Charlie

On Wed, Jul 18, 2012 at 4:15 AM, Dunken
<email address hidden> wrote:
> Question #203311 on NUnit V2 changed:
> https://answers.launchpad.net/nunitv2/+question/203311
>
> Dunken gave more information on the question:
> Hi Charlie
>
> It seems like it's because I called Console.WriteLine() in one of my
> tests. Am I not supposed to use it?
>
> Regards,
>
>
> ________________________________
>  Von: Galliker Armin <email address hidden>
> An: "<email address hidden>" <email address hidden>
> Gesendet: 8:20 Dienstag, 17.Juli 2012
> Betreff: Re: [Question #203311]: x86 Console crash
>
>
> Hi Charlie
>
> Yes, here's the stack trace:
>
>>    mscorlib.dll!System.IO.__Error.WinIOError(int errorCode = 6, string maybeFullPath = "") + 0x498 bytes
>      mscorlib.dll!System.IO.__ConsoleStream.Write(byte[] buffer, int offset, int count) + 0x15e bytes
>      mscorlib.dll!System.IO.StreamWriter.Flush(bool flushStream, bool flushEncoder) + 0x60 bytes
>      mscorlib.dll!System.IO.StreamWriter.Write(char[] buffer = {char[574]}, int index = 256, int count = 318) + 0xa2 bytes
>      mscorlib.dll!System.IO.TextWriter.WriteLine(string value) + 0xa1
>  bytes
>      mscorlib.dll!System.IO.TextWriter.WriteLine(string format, object arg0) + 0x49 bytes
>      mscorlib.dll!System.IO.TextWriter.SyncTextWriter.WriteLine(string format, object arg0) + 0x22 bytes
>      mscorlib.dll!System.Console.WriteLine(string format, object arg0) + 0x1b bytes
>      nunit-console-runner.dll!NUnit.ConsoleRunner.Runner.Main(string[] args) + 0x414 bytes
>      nunit-console-x86.exe!NUnit.ConsoleRunner.Class1.Main(string[] args) + 0x6 bytes
>
>
> Regards,
>
>
> ________________________________
>  Von: Charlie Poole <email address hidden>
> An: <email address hidden>
> Gesendet: 22:45 Montag, 16.Juli 2012
> Betreff: Re: [Question #203311]: x86 Console crash
>
> Your question #203311 on NUnit V2 changed:
> https://answers.launchpad.net/nunitv2/+question/203311
>
>    Status: Open => Needs information
>
> Charlie Poole requested more information:
> Clearly it's some sort of IO error. Can you provide a stack trace?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/nunitv2/+question/203311
>
> You received this question notification because you asked the question.
>
> You received this question notification because you are an answer
> contact for NUnit V2.

--
If this answers your question, please go to the following page to let us
know that it is solved:
https://answers.launchpad.net/nunitv2/+question/203311/+confirm?answer_id=3

If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https://answers.launchpad.net/nunitv2/+question/203311

You received this question notification because you asked the question.

Revision history for this message
Launchpad Janitor (janitor) said : 		#6

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Dunken (mc-ghc) said : 		#7

I still have this issue. Anything I could try out?

Revision history for this message
Launchpad Janitor (janitor) said : 		#8

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Dunken (mc-ghc) said : 		#9

Do you want me to provide any additional information? We're stuck with this...

Revision history for this message
Charlie Poole (charlie.poole) said : 		#10

I didn't see your post of 7/25.. I'll examine the log and get back to you.

Revision history for this message
Launchpad Janitor (janitor) said : 		#11

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Dunken (mc-ghc) said : 		#12

...still an issue...

Can you help with this problem?

Provide an answer of your own, or ask Dunken for more information if necessary.

To post a message you must log in.