Skip to content

Race conditions when using 'tox --parallel' #1514

Open
@kenahoo

Description

@kenahoo

Describe the bug
I've been getting a lot of errors about "no such table" or "table already exists" when trying to run tox with coverage reporting. It looks a fair amount like #1303, but I'm opening a new issue because it looks like at least one problem was already solved in that ticket, and the existing issue has gotten kind of complicated over time.

This means that users can't use parallel testing at the same time as coverage reporting.

To Reproduce

  1. Check out the minimal project I created to show the bug:
    git clone [email protected]:kenahoo/pkg-test-coverage-bug.git
  2. Have a working version of python 3.8 and 3.9 available to tox.
  3. Run python -m tox and (hopefully) observe that everything passes.
  4. Run python -m tox --parallel auto and (hopefully) observe that things fail with the above errors.

If the above doesn't demonstrate the problem, I can try to provide additional context, let me know.

Notes
This is important in my organization, because we need to assure compatibility with several dependency chains, and the tests take a while, so parallel testing is very important to get timely feedback.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions