[ 
https://issues.apache.org/jira/browse/PHOENIX-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103273#comment-15103273
 ] 

Karan Singhal commented on PHOENIX-2592:
----------------------------------------

[~giacomotaylor]- The change which solves this jira's issue are there in the 
patch applied. The reason now test is failing is altogether different case that 
is dates are not properly parsed from xml in some environments. I am curios to 
know why it's happening so working on the fix maybe   it's related to different 
JAXB or jdk versions but not sure so need little more time to find out. 

Yes, we can definitely put the ignore tag for test until the issue is resolved. 
Should I submit a new patch with just ignore tag in that?  
 

> Pherf RuleGeneratorTest.testDateGenerator() is flapping
> -------------------------------------------------------
>
>                 Key: PHOENIX-2592
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2592
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.6.0
>            Reporter: James Taylor
>            Assignee: Karan Singhal
>              Labels: Performance
>             Fix For: 4.6.0, 4.7.0
>
>         Attachments: PHOENIX-2592.patch
>
>
> See https://builds.apache.org/job/Phoenix-4.x-HBase-1.0/315/changes
> {code}
> Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.807 sec <<< 
> FAILURE! - in org.apache.phoenix.pherf.RuleGeneratorTest
> testDateGenerator(org.apache.phoenix.pherf.RuleGeneratorTest)  Time elapsed: 
> 0.373 sec  <<< FAILURE!
> java.lang.AssertionError: Value 2019-09-22T00:01:00.000Z is not after minValue
>       at 
> org.apache.phoenix.pherf.RuleGeneratorTest.assertDateBetween(RuleGeneratorTest.java:259)
>       at 
> org.apache.phoenix.pherf.RuleGeneratorTest.assertRandomDateValue(RuleGeneratorTest.java:133)
>       at 
> org.apache.phoenix.pherf.RuleGeneratorTest.testDateGenerator(RuleGeneratorTest.java:57)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to