[jira] [Resolved] (AVRO-2244) Problems with TestSpecificLogicalTypes.testAbilityToReadJsr310RecordWrittenAsJodaRecord:148

["Fokko Driesprong (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AVRO-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fokko Driesprong resolved AVRO-2244.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

> Problems with TestSpecificLogicalTypes.testAbilityToReadJsr310RecordWrittenAsJodaRecord:148
> -------------------------------------------------------------------------------------------
>
>                 Key: AVRO-2244
>                 URL: https://issues.apache.org/jira/browse/AVRO-2244
>             Project: Apache Avro
>          Issue Type: Bug
>          Components: logical types
>            Reporter: Raymie Stata
>            Assignee: Thiruvalluvan M. G.
>            Priority: Major
>             Fix For: 1.9.0
>
>
> I've seen an intermittent test failure that looks like this:
> {{Failed tests:}}
> {{  TestSpecificLogicalTypes.testAbilityToReadJsr310RecordWrittenAsJodaRecord:148}}
> {{Expected: is "20:35:18.720"}}
> {{     but: was "20:35:18.72"}}
> When I see this failure, it's always the case that the trailing digit is zero.  I suspect that it's a bug where the trailing zero is not printed.  Since the test cases use the current time, then most of the time the trailing digit isn't zero and the bug isn't tickled.  But once-in-a-while the current time has a trailing zero, which tickles the bug.
> If this diagnosis is correct, then in addition to fixing the bug, it might be a good idea to add tests with hard-wired, static times that cover corner cases like this one.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)