#290: Provide concurrency-safe way of executing tests -------------------------+-------------------------------------------------- Reporter: kparal | Owner: Type: enhancement | Status: new Priority: major | Milestone: 0.5.0 Component: core | Keywords: -------------------------+-------------------------------------------------- There is already ticket #248 that talks about problems when two depcheck tests are running at the same time. But this problem is not just about depcheck, it applies generally to all tests that handle multiple packages (probably whole repo or similar) at once. We have to provide some option for these tests to specify that either only one such test can run at a time or the older run results can't beat the newer run results (will resultdb solve it effortlessly?).
I'm creating new ticket for this in case we do some kind of depcheck hack first (issue #248) and provide proper solution for general tests later on.
#290: Provide concurrency-safe way of executing tests -------------------------+-------------------------------------------------- Reporter: kparal | Owner: Type: enhancement | Status: new Priority: major | Milestone: 0.5.0 Component: core | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by kparal):
Until we have a solution, I have decreased the frequency of koji watcher runs to once every 30 minutes (commit 495a213b6e79b48bdfb39e7befa01d18955fefbf).
#290: Provide concurrency-safe way of executing tests -------------------------+-------------------------------------------------- Reporter: kparal | Owner: Type: enhancement | Status: new Priority: major | Milestone: Future tasks Component: core | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by kparal):
* milestone: 0.5.0 => Future tasks
autoqa-devel@lists.fedorahosted.org