Bug 6403 - TimeSpan uses incorrect rounding when rounding to the nearest millisecond
Summary: TimeSpan uses incorrect rounding when rounding to the nearest millisecond
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib ()
Version: master
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-08-05 23:55 UTC by Martin Potter
Modified: 2012-08-09 05:13 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Martin Potter 2012-08-05 23:55:27 UTC
When creating a TimeSpan, the documentation states that it will only be accurate to the nearest millisecond. Microsoft's implementation rounds to the nearest millisecond, away from zero; Mono currently uses the default bankers rounding. To reproduce, run the following code:





Comment 1 Martin Potter 2012-08-06 00:06:55 UTC
Submitted pull request with fix, https://github.com/mono/mono/pull/418