[ https://issues.apache.org/jira/browse/AVRO-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16691177#comment-16691177 ]
Thiruvalluvan M. G. commented on AVRO-2244: ------------------------------------------- I showed how to deterministically reproduce the problem [here|https://github.com/thiru-apache/avro/commit/97fb7c28a886384482ecafe7dad0281c10357bc4] > 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 > > 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)