Notes |
|
(0122786)
|
hgbot
|
2020-09-08 11:40
|
|
|
|
(0122893)
|
hgbot
|
2020-09-10 07:06
|
|
Directly closing issue as related merge request is already approved.
Repository: https://gitlab.com/openbravo/product/openbravo [^]
Changeset: 9c038fa5404812da14fc7c887947f8b0c5111780
Author: Cristian Berner <cristian.berner@openbravo.com>
Date: 2020-09-10T05:05:23+00:00
URL: https://gitlab.com/openbravo/product/openbravo/-/commit/9c038fa5404812da14fc7c887947f8b0c5111780 [^]
Fixes ISSUE-45006: Stabilize MisfirePolicyTest when clustered
MisfirePolicyTest checkMisfirePolicyWithSecondlySchedule was not waiting
enough for the execution of the expected 2 jobs. MisfireHandler checks every
second for missed jobs to execute. A lower time for the misfireHandler has been set, 500ms
and delay has been set to 3 seconds.
Also because of this, a race condition was happening when using
Dal transaction to access Lock table by quartz, it should not happen as
misfireHandler has plenty time to check and execute jobs now.
---
M src-test/src/org/openbravo/scheduling/trigger/MisfirePolicyTest.java
---
|
|
|
(0122894)
|
hgbot
|
2020-09-10 07:06
|
|
|
|
(0123070)
|
hgbot
|
2020-09-15 16:55
|
|
|
|
(0123081)
|
hgbot
|
2020-09-16 07:07
|
|
|
|
(0123082)
|
hgbot
|
2020-09-16 07:07
|
|
|
|
(0123557)
|
hgbot
|
2020-10-05 17:53
|
|
|
|
(0123660)
|
hgbot
|
2020-10-09 14:58
|
|
Repository: https://gitlab.com/openbravo/product/openbravo [^]
Changeset: 135c5be70963d2e930090c7d6861e143fd4d3087
Author: Cristian Berner <cristian.berner@openbravo.com>
Date: 2020-10-09T14:48:05+02:00
URL: https://gitlab.com/openbravo/product/openbravo/-/commit/135c5be70963d2e930090c7d6861e143fd4d3087 [^]
Related to ISSUE-45006: Stabilize MisfirePolicyTest tests in clustered mode
Tests in MisfirePolicyTest class were unstable in CI and as such, some
parts have been implemented with this in mind. scheduleJob method will
try to schedule a job and if it fails, it will retry after 1 second,
until it reaches maximum time of 10 seconds.
This will allow to handle some of the race-conditions that were
happening in CI in this issue.
Also, now those tests will test that the trigger has correctly misfired,
that was previously implied, but now it is actually tested using a
TriggerListener. Also waiting some time if the misfire was not
detected on the first 500ms. The maximum wait time is defined in
MAX_WAIT constant.
---
M src-test/src/org/openbravo/scheduling/trigger/MisfirePolicyTest.java
---
|
|
|
(0123661)
|
hgbot
|
2020-10-09 14:58
|
|
|
|
(0126123)
|
hgbot
|
2021-02-16 10:11
|
|
|
|
(0126163)
|
hgbot
|
2021-02-18 14:47
|
|
Repository: https://gitlab.com/openbravo/product/openbravo [^]
Changeset: 16d7adc08764f2fd9da0a9cdbd5bb25d685012f4
Author: Cristian Berner <cristian.berner@openbravo.com>
Date: 2021-02-16T10:10:37+01:00
URL: https://gitlab.com/openbravo/product/openbravo/-/commit/16d7adc08764f2fd9da0a9cdbd5bb25d685012f4 [^]
Related to ISSUE-45006: Stabilize MisfirePolicyTest tests in clustered mode
Tests in MisfirePolicyTest class were unstable in CI and as such, some
parts have been implemented with this in mind. scheduleJob method will
try to schedule a job and if it fails, it will retry after 1 second,
until it reaches maximum time of 10 seconds.
This will allow to handle some of the race-conditions that were
happening in CI in this issue.
Also, now those tests will test that the trigger has correctly misfired,
that was previously implied, but now it is actually tested using a
TriggerListener. Also waiting some time if the misfire was not
detected on the first 500ms. The maximum wait time is defined in
MAX_WAIT constant.
---
M src-test/src/org/openbravo/scheduling/trigger/MisfirePolicyTest.java
---
|
|
|
(0126164)
|
hgbot
|
2021-02-18 14:47
|
|
|