Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Possible bug in Nunit extension?
-
I have encountered a weird issue with the NUnit extension. I have included a section of the log file below.
I was wondering that have I misconfigured something is this a possible bug?
I think that the error is caused by the decimal symbol which is in Finnish locale comma (,) and not dot (.) and I would guess that the issue is caused by the double.Parse() -method in the NUnitAppAction.cs file on line 128.
https://github.com/Inedo/bmx-nunit/blob/master/NUnitAppAction.csHere is the log output for the NUnit action:
<pre>
Action 3: Run NUnit Unit Tests on src\CmdParser.Tests\bin\Debug\Orchidea.CmdParser.Tests.dll
Running unit tests...
NUnit version 2.5.10.11092
Copyright (C) 2002-2009 Charlie Poole.
Copyright (C) 2002-2004 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov.
Copyright (C) 2000-2002 Philip Craig.
All Rights Reserved.
Runtime Environment -
OS Version: Microsoft Windows NT 6.1.7601 Service Pack 1
CLR Version: 2.0.50727.5477 ( Net 2.0 )
ProcessModel: Default DomainUsage: Single
Execution Runtime: Default
............................
Tests run: 28, Errors: 0, Failures: 0, Inconclusive: 0, Time: 0,8421354 seconds
Not run: 0, Invalid: 0, Ignored: 0, Skipped: 0
An unhandled exception occurred while executing this action: System.FormatException: Input string was not in a correct format. at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt) at Inedo.BuildMasterExtensions.NUnit.NUnitAppAction.RunTests() at Inedo.BuildMaster.Extensibility.Actions.Testing.UnitTestActionBase.Execute() at Inedo.BuildMaster.Extensibility.Actions.ActionBase.ExecuteInternal(IActionExecutionContext context, ExtensionConfigurerBase extensionConfigurer, Boolean resumeNextOnError, Boolean logErrorsAsWarnings)
</pre>Product: BuildMaster
Version: 4.1.5
-
I believe someone from our support staff emailed you a quick fix for this. It appears the
double.Parse()
method was not taking the current NumberFormatInfo into account for some reason.