There is no workaround against a DB lock, the issue we are facing on the project. We would do some stuff to avoid doing things in parallel but decided to not take that route if something is meant to run things in parallel then the database should support it.
Instead we are lowering the percentage of success that we expect for the automation. We were looking for 100% before. On Thu, Apr 26, 2018 at 11:49 AM Preethi Thomas <[email protected]> wrote: > Recently Elyezer was talking about a possible workaround for automation. > > On Thu, Apr 26, 2018 at 10:29 AM, Jeremy Audet <[email protected]> wrote: > >> +1 to switching away from SQLite. I've often pondered a failed test and >> wondered "is this a genuine bug, or a side-effect of using SQLite?" This >> question is suspiciously similar to "is this a genuine bug, or a >> side-effect of using Mongo?" >> >> For more information on SQLite and concurrency, see isolation in SQLite >> <https://sqlite.org/isolation.html>. >> >> _______________________________________________ >> Pulp-dev mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/pulp-dev >> >> >
_______________________________________________ Pulp-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-dev
