Details
-
Bug Report
-
Resolution: Unresolved
-
L3 - Default
-
None
-
7.16.0, 7.17.0
-
None
Description
Environment (Required on creation):
- Set the timezone of the build environment to UTC.
- Use any Camunda-supproted DB (tested with MS-SQL, H2 and PostgreSQL).
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):
The following tests fail during a date assertion:
[ERROR] HistoryCleanupSchedulerActivityInstancesTest.shouldScheduleToLater:130 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerAttachmentsTest.shouldScheduleToLater:148 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] org.camunda.bpm.engine.test.api.history.removaltime.cleanup.HistoryCleanupSchedulerAuthorizationsTest.shouldScheduleToLater(org.camunda.bpm.engine.test.api.history.removaltime.cleanup.HistoryCleanupSchedulerAuthorizationsTest) [ERROR] Run 1: HistoryCleanupSchedulerAuthorizationsTest.shouldScheduleToLater:153 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerBatchesTest.shouldScheduleToLater:173 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerCommentsTest.shouldScheduleToLater:146 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerDecisionsTest.shouldScheduleToLaterByDecisionInputs:141 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerDecisionsTest.shouldScheduleToLaterByDecisionOutputs:201 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerDetailsTest.shouldScheduleToLater:141 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerExternalTaskLogsTest.shouldScheduleToLater:156 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerIdentityLinkLogsTest.shouldScheduleToLater:137 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerIncidentsTest.shouldScheduleToLater:165 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerJobLogTest.shouldScheduleToLater:161 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerProcessInstancesTest.shouldScheduleToLater:135 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerTaskInstancesTest.shouldScheduleToLater:140 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerTaskMetricsTest.shouldScheduleToLater:133 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerUserOperationLogsTest.shouldScheduleToLater:149 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000> [ERROR] HistoryCleanupSchedulerVariableInstancesTest.shouldScheduleToLater:139 expected:<2013-03-23T1[2:00:1]0.000> but was:<2013-03-23T1[3:00:0]0.000>
Steps to reproduce (Required on creation):
- Set the build environment timezone to UTC.
- Run any of the HistoryCleanupScheduler* tests.
Observed Behavior (Required on creation):
Some of the tests in the org.camunda.bpm.engine.test.api.history.removaltime.cleanup package fail with a bad Date assertion.
Expected behavior (Required on creation):
The tests don't fail when the UTC timezone is used.
Root Cause (Required on prioritization):
It is currently not clear why these tests fail.
Solution Ideas (Optional):
Updating the value of AbstractHistoryCleanupSchedulerTest.END_DATE from 1363608000000L (Mar 18 2013 12:00:00) to 1625072830L (Jun 30 2021 17:07:10) fixes the issue.