Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-4750

Test case fails from time to time: HistoricDecisionInstanceTest

    XMLWordPrintable

    Details

    • Type: Bug Report
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: 7.4.0-alpha2
    • Fix Version/s: 7.4.0, 7.4.0-alpha3
    • Component/s: engine
    • Labels:

      Description

      The test verifies time order of historic tasks. Since the resolution is ms, the order my not predictable if the engine is faster to complete the tasks.

      On my computer I inserted a calculation to show the distance between to tasks: 3 ms.

      Stephan Itzenplitz could not compile and test camunda bpmn, his computer is probably a little bit faster. He did all the analyze work to locate the problem. Compilation within Ecipse slows the process so that there have been no problems.

      Please have a look at the following test case:

      testMultipleDecisionInstances

          startProcessInstanceAndEvaluateDecision("a");
          try {
              Thread.sleep(5);
          } catch (InterruptedException e) {
              // will not happen
              e.printStackTrace();
          }
          startProcessInstanceAndEvaluateDecision("b");
      

      If you run it with the Thread.sleep call, it is ensured, that there will be the required delay on milli second level to get it all time working.

      Caution:
      Please think about concepquences.

      • Is the resolution at the API sufficient?
      • are there probably further tests affected?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              MatthiasBrenner Matthias Brenner
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: