You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Serge Huber (Jira)" <ji...@apache.org> on 2022/05/30 13:04:00 UTC

[jira] [Created] (UNOMI-579) Issue with ConditionEvaluatorIT on certain platforms

Serge Huber created UNOMI-579:
---------------------------------

             Summary: Issue with ConditionEvaluatorIT on certain platforms
                 Key: UNOMI-579
                 URL: https://issues.apache.org/jira/browse/UNOMI-579
             Project: Apache Unomi
          Issue Type: Bug
          Components: core
    Affects Versions: 2.0.0
            Reporter: Serge Huber
             Fix For: 2.0.0


It seems that on some platforms, the ConditionEvaluatorIT date test fails with the following error:

{code}
[ERROR] Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 273.548 s <<< FAILURE! - in org.apache.unomi.itests.ConditionEvaluatorIT
[ERROR] org.apache.unomi.itests.ConditionEvaluatorIT.testDate  Time elapsed: 224.73 s  <<< FAILURE!
java.lang.AssertionError
	at org.apache.unomi.itests.ConditionEvaluatorIT.testDate(ConditionEvaluatorIT.java:123)
{code}

I tried to debug this and it is very strange because it seems to be related to the way the days "distance" is evaluated and somehow seems to be related to timezones. I'm suspecting this because this test works fine on the Github CI server that are (probably) using GMT but it fails locally on my computer that is using GMT+1. 

This is, however, just my best guess at this point. I tried debugging this test but couldn't find a clear explanation. It could also be some kind of bug with the JodaMathParser or the JVM date implementation as well.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)