Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-4175 AutoQA Bug Fixing
  3. TRANSLATE-3906

manual start of AutoQA should not mind lock state

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • None
    • None
    • Auto-QA
    • Medium
    • FIXED: AutoQA now applies lock state only of not already locked

      Problem

      When starting the AutoQA and another user has opened the task (and locks it) the AutoQA will not run

      Solution

      When a task is locked and someone starts an Auto-QA, the Operation shall start with a new Worker "Start delayed Operation" (general implementation for all Operations). This Worker is queued with the state "delayed" and waits for the task to be unlocked. When the task is unlocked, the worker locks it, sets the operation state and queues the Operation (just what happens now when the start operation request is done).

      • The worker has the task-guid and the desired operation-type as param
      • It is queued with a delay of 120 seconds each time (override ::calculateDelay)
      • when the delay is done, the worker checks, if the task is unlocked now, if yes, it starts the operation, if not, it delays itself again
      • After 4h max delay time the worker terminates and writes an warning-event for the task the Operation could not be started and sends a message to the user that requested the operation via the messagebus

            pavelperminov Pavel Perminov
            sylviaschumacher Sylvia Schumacher
            Axel Becher
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: