[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#c4


Andy Hume <andyhume32 at yahoo.co.uk> changed:

           What    |Removed                                         |Added
----------------------------------------------------------------------------
 Attachment #227819|0                                               |1
        is obsolete|                                                |




--- Comment #4 from Andy Hume <andyhume32 at yahoo.co.uk>  2008-09-10 02:22:25 MDT ---
Created an attachment (id=238801)
 --> (https://bugzilla.novell.com/attachment.cgi?id=238801)
Patch #2

Sorry about that!  I must have added that first test case after I did my "other
timezone" test run, as that DateTimeOffset constructor uses the ambient
timezone, so that test case is a not usable around the world[1].

So I disable it out similarly to the last case.  New patch attached.


BTW In testing I noticed that ParseExactDatesOnly and ParseExactYearFormat fail
on MSFT (run-test-ondotnet).


[1] Some logging from the test run, shows that its the offset in the
DateTimeOffset in the test case that's wrong, and not the result of the
deserialization that's wrong.  (Run in Central TZ).

#0 input.o/s : -06:00:00
#0 result.o/s: 00:00:00
#0 input.dt : 1/2/2007 12:30:50 PM=Tue, 02 Jan 2007 12:30:50 GMT=2007-01-02
12:30:50Z
#0 result.dt: 1/2/2007 12:30:50 PM=Tue, 02 Jan 2007 12:30:50 GMT=2007-01-02
12:30:50Z
#0 input.dtK: Unspecified
#0 input : 1/2/2007 12:30:50 PM -06:00=Tue, 02 Jan 2007 18:30:50 GMT=2007-01-02
18:30:50Z
#0 result: 1/2/2007 12:30:50 PM +00:00=Tue, 02 Jan 2007 12:30:50 GMT=2007-01-02
12:30:50Z


-- 
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.