Make test database template creation concurrent build_db_cache() is used in tests to create test database templates, i.e. DEFAULT_EMPTY_DB_ID (which is __default_empty_db__) and custom template database using CubicwebTC test_db_id/pre_setup_database API. When running tests in parallel using multiple processes, build_db_cache() may try to build the same database twice. Avoid this by adding synchronisation of process by using a file lock. So when two processes require the same template database, one build the database and others wait it to be created. Use filelock (https://github.com/benediktschmitt/py-filelock) library to have a portable (unix / windows) way for handling locks. Also filelock is packaged in debian: https://packages.debian.org/source/python-filelock

     1

### Requirements for tests in various cubicweb/**/test directories. ###

     2

     3

## shared by several test folders

     4

cubicweb-card == 0.5.8

     5

docutils

     6

Twisted < 16.0.0

     7

webtest

     8

     9

## cubicweb/test

    10

Pygments

    11

mock

    12

#fyzz XXX pip install fails

    13

cubicweb-file == 1.18.0

    14

cubicweb-localperms == 0.3.2

    15

cubicweb-tag == 1.8.3

    16

    17

## cubicweb/devtools/test

    18

flake8

    19

    20

## cubicweb/hooks/test

    21

psycopg2

    22

    23

## cubicweb/pyramid/test

    24

pyramid >= 1.5.0

    25

waitress >= 0.8.9

    26

wsgicors >= 0.3

    27

pyramid_multiauth

    28

    29

## cubicweb/sobject/test

    30

cubicweb-comment == 1.12.2