Investigate flaky concurrent removal time test

XMLWordPrintable

    • Type: Task
    • Resolution: Unresolved
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: engine

      Acceptance Criteria (Required on creation):

      • We have a good understanding as to why the test case RemovalTimeStrategyEndTest#shouldResolveHistoricActivityInstanceInConcurrentEnvironment is failing randomly only on MariaDB, MySQL and CockroachDB.

      Hints (Optional):

      • The test case has been introduced with CAM-13094 to ensure we prevent deadlocks on MSSQL on concurrent removal time updates
      • Those deadlocks are randomly occurring on MariaDB, MySQL and CockroachDB for that test case
      • The test case has been disabled on MariaDB, MySQL and CockroachDB for now
      • The test case has been added to 7.14 and 7.15 with CAM-13094 but might be present on other versions as well in the meantime if there was a need to patch this further down

            Assignee:
            Unassigned
            Reporter:
            Tobias Metzke-Bernstein
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: