You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the toxenv after all option looks at the TOXENV environment variable. This is mostly useful, because it's quite common to set that environment variable to control tox, and tox-travis uses it under the hood.
However, it fails in a couple of cases:
No TOXENV is set. This is mostly a non-concern for us, because we always set it.
-e env is given to tox. This is the more annoying part, because it might be used. It's a reasonable limitation for a first version, but there's probably going to be someone somewhere that is surprised by this, and I won't blame them.
What I'd like to do, if possible, is inspect Tox's run somehow, so that I know which envs were actually run, and match against those instead of relying on the environment variable.
The text was updated successfully, but these errors were encountered:
ryanhiebert
changed the title
Let toxenv match actually run environments
Let toxenv match run environments
Dec 21, 2016
ryanhiebert
changed the title
Let toxenv match run environments
Make toxenv match run environments
Dec 21, 2016
Currently the
toxenv
after all option looks at the TOXENV environment variable. This is mostly useful, because it's quite common to set that environment variable to control tox, and tox-travis uses it under the hood.However, it fails in a couple of cases:
-e env
is given totox
. This is the more annoying part, because it might be used. It's a reasonable limitation for a first version, but there's probably going to be someone somewhere that is surprised by this, and I won't blame them.What I'd like to do, if possible, is inspect Tox's run somehow, so that I know which envs were actually run, and match against those instead of relying on the environment variable.
The text was updated successfully, but these errors were encountered: