Aymeric, did you envision any changes to Django's CI setup? Currently we run 1 Jenkins executor per CPU, so I don't know that adding parallelization would have any benefit? (We are already using all 8 CPUs when we're running 8 concurrent builds from the matrix.) If not, then I wonder how we can ensure that Django's test suite continues to work well in parallel.
On Monday, August 31, 2015 at 4:11:29 AM UTC-4, Aymeric Augustin wrote: > > Hi Tino, > > 2015-08-31 8:35 GMT+02:00 Tino de Bruijn <tin...@gmail.com <javascript:>>: > >> - What happens when two SerializeMixin tests try to lock the same file? >> Does one wait for the other (probably not), or is a lockfile exception >> raised? >> > > The second one waits for the first one to complete. This happens all the > time because conflicting tests are often defined close to one another and > the parallel test runner runs tests in order. > > >> - How does this work in combination with the --keepdb flag >> > > All clones of the test database are kept. > > There's one edge case: if you run with --parallel-num=2 --keepdb and then > --parallel-num=4 --keepdb, the test runner will crash because clones 3 and > 4 won't exist. I don't think that's a big problem. > > -- > Aymeric. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/4c827092-f990-4ea8-9960-dd4b86fbe980%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
