[Mono-bugs] [Bug 409181] [PATCH] Implement DateTimeOffset runtime-serialization

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=409181

User andyhume32 at yahoo.co.uk added comment
https://bugzilla.novell.com/show_bug.cgi?id=409181#c7





--- Comment #7 from Andy Hume <andyhume32 at yahoo.co.uk>  2008-09-15 12:53:24 MDT ---
Created an attachment (id=239655)
 --> (https://bugzilla.novell.com/attachment.cgi?id=239655)
corlib's TestResult-ondotnet-net_2_0.log

'make PROFILE=net_2_0 run-test-ondotnet' on the DateTimeOffsetTest test fixture
produces:
[[
Tests run: 28, Failures: 2, Not run: 0, Time: 0.140625 seconds

Failures:
1) MonoTests.System.DateTimeOffsetTest.ParseExactDatesOnly :
System.FormatException : String was not recognized as a valid DateTime.
   at System.DateTimeParse.ParseExact(String s, String format,
DateTimeFormatInfo dtfi, DateTimeStyles style, TimeSpan& offset)
   at System.DateTimeOffset.ParseExact(String input, String format,
IFormatProvider formatProvider, DateTimeStyles styles)
   at System.DateTimeOffset.ParseExact(String input, String format,
IFormatProvider formatProvider)
   at MonoTests.System.DateTimeOffsetTest.ParseExactDatesOnly()

2) MonoTests.System.DateTimeOffsetTest.ParseExactYearFormat :
System.FormatException : String was not recognized as a valid DateTime.
   at System.DateTimeParse.ParseExact(String s, String format,
DateTimeFormatInfo dtfi, DateTimeStyles style, TimeSpan& offset)
   at System.DateTimeOffset.ParseExact(String input, String format,
IFormatProvider formatProvider, DateTimeStyles styles)
   at System.DateTimeOffset.ParseExact(String input, String format,
IFormatProvider formatProvider)
   at MonoTests.System.DateTimeOffsetTest.ParseExactYearFormat()

]]

In both cases it apparently fails on the three-digit year case "M/d/yyy".


In total, "run-test-ondotnet" there has 121 failures (log attached).  However
Mono on Windows itself has 24 failures, probably half being path separator
related.  BTW (again!) on Mono/Windows the unit-test app never exits, which is
presumably the cause of the many '** Terminating process because no output for
1200 second(s)**' statuses on the Windows build bot and contributes to the very
long cycle time there.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.