A last (?) regression on the Scheduler capture count. - Use a sequence file with 5-second 3xR 3xG 3xR. - Execute Scheduler on this sequence, wait for it to finish. - Remove one Red capture. - Refresh Scheduler plan, missing capture is spotted. - Execute Scheduler plan, Frame Map summary is wrong and 3 Red captures are processed.
Two possible extensions to this issue from @wreissenberger: "The setup is the following: create a schedule with two jobs for the same target with the same sequence job (say 1xLum for example). The first job starts and captures the first frame. And here is where the problem occurs: now calling Scheduler::updateCompletedJobsCount() detects the one frame, but when evaluating the second job (which did not run yet), the value in the captured frames map is overwritten. This leads to an endless loop of the first job." "I observed that the counting update happens only after a single sequence is finished and not after each capture."
Created attachment 114674 [details] Test case for the looping first job issue
Created attachment 114675 [details] Test case for the frame count updating at each of sequence
For FIRST EXTENSION of this issue: "This leads to an endless loop of the first job". Proposed hotfix at https://phabricator.kde.org/D15230.
Will verify this issue with Capture tests soon.