nunit-core team mailing list archive
-
nunit-core team
-
Mailing list archive
-
Message #00602
[Bug 597265] Re: 2.5.5 x64 net-4.0 crash
VS 2010 MS Test also crashes with the same unit tests. :) It also seems
to do it at the same location as the Nunit crash.
Application Name: QTAgent.exe
Application Version: 10.0.30319.1
Application Timestamp: 4ba20efa
Fault Module Name: msxml6.dll
Fault Module Version: 6.30.7600.16385
Fault Module Timestamp: 4a5bdfc8
Exception Code: c0000005
Exception Offset: 00000000000016d1
OS Version: 6.1.7600.2.0.0.272.7
Locale ID: 3081
Additional Information 1: 3cfc
Additional Information 2: 3cfc6c6d14bdc651a9c8274b1b406d59
Additional Information 3: edd5
Additional Information 4: edd5622e8ad533d3357f6496dc3c65f4
Looks like it's an MS bug in x64. Reading excel files individually
seems to pass unit tests, but if you have a class that reads excel files
and you re-use that to read multiple excel files the application crashes
in Windows x64, but doesn't in a x86 environment.
--
2.5.5 x64 net-4.0 crash
https://bugs.launchpad.net/bugs/597265
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
Status in NUnit V2 Test Framework: New
Bug description:
Running x64 based unit tests on x64 Windows Server 2008 R2. Get the following crash from VS2010 automating Nunit.exe.
Testing Office 2010 Excel reading with x64 drivers. Running a single test works ok. Running a set of Excel tests causes the application crash. I suspect MS bug in the x64 data drivers, but this is the offending nunit test.
' Sheet Name and Row/Column Reference
Console.WriteLine(String.Format(cNunitMessage, "Sheet Name and Row/Column Reference"))
objDS = objExcel.GetDataSet(System.IO.Path.Combine(GetCurrentPath, "TestData\WithDataInSheet1.xlsx"), "Sheet1$B2:D10")
If objDS.Tables.Count = 0 Then
Assert.Fail("No data returned")
End If
If I run the nunit test by itself it works as expected. If I run all the tests in the nunit class it fails and crashes Nunit. The crash sends a lot of information to Microsoft.
Follow ups
References