Re: [AutoQA] #342: Prevent duplicate tests from being scheduled
#342: Prevent duplicate tests from being scheduled
----------------------+-----------------------------------------------------
Reporter: tflink | Owner:
Type: defect | Status: new
Priority: major | Milestone: 0.5.0
Component: watchers | Resolution:
Keywords: |
----------------------+-----------------------------------------------------
Comment (by jskladan):
Replying to [comment:2 jlaska]:
I like this solution, but I'm curious why an extra lock file
would be
needed.
Well, it's not needed. As I said to Kamil, this is "just an
implementation" of locking. Basically to determine whether the problem
really is in the concurrent runs.
I personaly like lock file a bit more, because you can easily see whether
the lock is active or not, and also which process has the lock (just by
looking at/into the lockfile). But I'm not against using different
approach, if you think it's more suitable.
The only thing I don't like about lockf/flock is lack of examples in the
python documentation. And that's probably _the_ reason why I used lockfile
- it was faster for me to grasp/implement.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/342#comment:3>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project