Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixing status flaky test #3777

Merged
merged 2 commits into from
Nov 15, 2024
Merged

Fixing status flaky test #3777

merged 2 commits into from
Nov 15, 2024

Commits on Nov 14, 2024

  1. Fixing status flaky test 

    There is a chance that status is invoked over a process instance that
has been finished, but the container kogito process instance does not
know yet, even if processcompleted listener has been executed (and thats
the issue)

Although this can be fixed by altering the order in which the different
listener are invoked (which might probably have other undesired effect),
I do not see a reason why status should not be read from underlying
process instance, if present.

Probably processInstance field should be embedded into an atomic
reference, but volatile might have the same effect with few code
changes.
    @fjtirado
    fjtirado committed Nov 14, 2024
    Configuration menu
    Copy the full SHA
    dfd99df View commit details
    Browse the repository at this point in the history

  2. Try changing order of listeners

    @fjtirado
    fjtirado committed Nov 14, 2024
    Configuration menu
    Copy the full SHA
    d852da7 View commit details
    Browse the repository at this point in the history