https://bugs.kde.org/show_bug.cgi?id=389738
--- Comment #9 from schwim <sch...@bitrail.com> --- (In reply to schwim from comment #8) > (In reply to Jasem Mutlaq from comment #7) > > Can you check with latest GIT if this issue is resolved? > > Built and testing in between imaging. Standby... Here's what I'm seeing for two different job completion conditions - Sequence Completion: Can re-run the job over and over - GOOD - Multiple jobs mixed of the two: seems to work fine - GOOD - Repeat for _N_ runs - will repeat N times as specified. An attempt to re-run this job (by restarting it) fails with "No valid jobs found, aborting..." message. If you edit the job and change N (e.g. N+1) it will run that new number of times. If you try to run it again, the same failure occurs. If you run the job several times to Sequence Completion as above, then switch to Repeat for ___ runs it will run. - Run one "N runs" job, deleted it, then re-add an identical job gives "observation job is already complete" message. One thing I noticed is if you have multiple jobs with "Repeat for __ runs" they all have to repeat the same number of times. You can't have one job repeat 2 times and another repeat 3 times, they both have to repeat the same number of times. I also noticed you can't edit the priority of a job once it is in the list. These are probably a different item to be tracked. I'll open bugs on those two independently if you prefer. -- You are receiving this mail because: You are watching all bug changes.
