Have some level of non-concurrency.

Issue #234 on hold
Matthew Schinckel created an issue

I have a really nice workflow for managing coverage testing using tox: I have an envlist that looks something like:


The first listed environment simply removes the existing coverage data, and the final one runs the coverage status reports.

The issue is that with detox, the env status runs before any of the other envs have had a chance to finish.

I'd love some way of either marking that a specific env should not run under detox (as it gives an error that no coverage data was found), or should run after everything else.

The only workaround I have come up with is to remove the status env from the envlist, and run tox -e status after detox.

Comments (2)

  1. Log in to comment