| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: Bernat Gabor <bgabor8@bloomberg.net>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
* expand section names
* fix linting
* Added changelog
* trim whitespaces around factor names
* added docs
|
| |
|
|
|
|
|
| |
* Fix exeception when command is empty
* simplify expression
* add changelog
|
| |
|
|
|
|
|
| |
* Fixed #1546
* Added Changelog
* Solved CI Failure
|
| |
|
|
|
|
|
|
|
| |
* Fix parsing of architecture in python interpreter name
* add myself to contributors
* added entry to changelog
* updated changelog filename
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* fix ValueError: max() arg is an empty sequence
When running `tox -l` with a tox.ini file not containing any default environments, instead of an empty output, an exception is raised:
```
$ tox -l
tox -l
Traceback (most recent call last):
File "/Users/jq/.pyenv/versions/py38/bin/tox", line 8, in <module>
sys.exit(cmdline())
File "/Users/jq/.pyenv/versions/3.8.1/envs/py38/lib/python3.8/site-packages/tox/session/__init__.py", line 44, in cmdline
main(args)
File "/Users/jq/.pyenv/versions/3.8.1/envs/py38/lib/python3.8/site-packages/tox/session/__init__.py", line 68, in main
exit_code = session.runcommand()
File "/Users/jq/.pyenv/versions/3.8.1/envs/py38/lib/python3.8/site-packages/tox/session/__init__.py", line 189, in runcommand
self.showenvs(all_envs=False, description=show_description)
File "/Users/jq/.pyenv/versions/3.8.1/envs/py38/lib/python3.8/site-packages/tox/session/__init__.py", line 293, in showenvs
show_envs(self.config, all_envs=all_envs, description=description)
File "/Users/jq/.pyenv/versions/3.8.1/envs/py38/lib/python3.8/site-packages/tox/session/commands/show_env.py", line 14, in show_envs
max_length = max((len(env) for env in (default + extra)))
ValueError: max() arg is an empty sequence
```
* trying to follow contributing guidelines
* add test, fails without merge, succeeds after
Signed-off-by: Bernat Gabor <bgabor8@bloomberg.net>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* solved #1509 #1540
* added test for fixed help command
* added changelog
* solved CI error
the problem is with psutil==5.7.0 in pypy .
* solved lint problem :confounded:
Co-authored-by: nkpro2000sr <naveennotes2000sr@gmail.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
At the moment it's unecessarily hard to specify a specific python
executable to use for a given spec. While mangling with the path
might work for environments for tox environments that require a python
differing the host tox python version; for environments matching the
host tox interpreter it's impossible to use any other interpreter than
what tox uses. Here we add a CLI argument (fallback to some environment
variable for CI usage) that allows the user to inject custom python
interpreters as step 1 of the discovery mechanism.
Signed-off-by: Bernat Gabor <bgabor8@bloomberg.net>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default, we run SIGKILL after 0.5 seconds. Most of the time is
enough. But if the interrupted command have a complex processes tree,
it might not be enough to propagate the signal.
In such case processes are left behind and never killed.
If theses processes use static network port or keep file open. Next
call of tox will fail until the all processes left behind are manually
killed.
This change adds some configuration to be able to config the timeout
before signals are sent.
If the approach work for you, I will polish the PR (doc+test)
|
| |
|
|
| |
Signed-off-by: Bernat Gabor <bgabor8@bloomberg.net>
|
| |
|
| |
a follow up to #1467
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Mark poetry tests as xfail on windows
* Update tests/integration/test_package_int.py
Co-Authored-By: Anthony Sottile <asottile@umich.edu>
* fix formatting
Signed-off-by: Bernat Gabor <bgabor8@bloomberg.net>
|
| |
|
|
|
|
|
|
|
|
| |
Fixes #1428
When running in Jenkins and using `setup.cfg`, tox would not fall back
to the [tox:tox] configuration properly. This was due to how the
fallback section name was calculated in this specific combination of
characteristics.
on-behalf-of: @ithaka <dane.hillard@ithaka.org>
|
| |
|
|
|
|
|
|
|
|
| |
* fix
Signed-off-by: Bernat Gabor <bgabor8@bloomberg.net>
* suppress proc related failures on pypy
Signed-off-by: Bernat Gabor <bgabor8@bloomberg.net>
|
| |
|
|
|
|
|
|
|
| |
This shouls avoid SSL failures with HTTP requests from pip, requests
or other libraries.
Also sorts existing values in order to make it easier to update the
list in the future.
Fixes: #1437
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the original interpreter [0] tox is called with is actually a pyvenv
it will set the `__PYVENV_LAUNCHER__` environment variable to the path of
pyvenv interpreter.
If tox configuration specifies `requires` and the requirements are not
satifsfied by [0], tox will create an intermediate virtual environment [1].
After setting up [1] tox will delegate the original call by spawning
a new [1] interpreter with the identical identical list of arguments.
It will also pass the value of `__PYVENV_LAUNCHER__` if present. This in turn
causes `sys.executable` to resolve to [0] instead of [1] therefore ignoring all
modifications including installed requirements.
The fix is to make sure that when [0] spawns [1], `__PYVENV_LAUNCHER__` is
removed from the environment.
|
| |
|
|
|
|
| |
`subprocess` reports a negative exit code for signals.
Still handle "128 + X" for processes indicating that they received a
signal themselves.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...but keep the TOX_PARALLEL_ENV variable for others to consume.
The problem with using environment variables to let tox know it's being run
as a parallel worker is the following:
Either you don't pass the environment variable, but the test frameworks and
test suites are unaware that tox is running in parallel.
This makes it hard for cases like pytest-django:
https://github.com/tox-dev/tox/pull/1139
Or you pass the environment variable, but it makes tox invoked within tox
think it is a parallel worker even when it isn't.
This makes it hard to test various tox plugins that invoke tox in their
integration test suite:
Fixes https://github.com/tox-dev/tox/issues/1444
By introducing two variables we can use one ("private", _TOX_PARALLEL_ENV) to
control the behavior of tox (and don't pass it) and another ("public",
TOX_PARALLEL_ENV) to let the tests and test frameworks know tox is running
in parallel (and pass it by default).
The integration test is a tad complicated invoking subprocess.Popen instead
of subprocess.run, to support Python 2.7 and 3.4.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
* Add explicit check for pypy venv
* Add changelog entry
* Add regression test for --recreate
|
| | |
|
| |
|
|
|
|
|
|
| |
(#1336)
* Use POSIX shell rules for creating posargs string on non-Windows platforms. Closes #1336
* pre-commit run --all-files
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
* Correct ``--result-json`` output with ``--parallel``. (#1295)
When using ``--parallel`` with ``--result-json`` the test results are now included the same way as with serial runs.
This is accomplished by generating json result output for each individual run and at the end copy the data into the main json result output.
* avoid duplication in code, improve coverage
|
| |
|
|
|
|
|
|
|
|
| |
* pep-514 implementation
* reorganize interpreter
* report failures
* report failures
|
| |
|
|
|
|
|
|
| |
* Adding TOX_PARALLEL_NO_SPINNER to disable spinner for CI tools.
* Adding unit tests for TOX_PARALLEL_NO_SPINNER env var.
* Updating CONTRIBUTORS and changelog for TOX_PARALLEL_NO_SPINNER env var.
|
| |
|
|
|
|
|
|
| |
(#1301)
* Fixed result of tox_get_python_executable not being used to make virtualenvs
* fix formatting and add changelog
|
| |
|
|
|
| |
package versions (#1298)
and package versions
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* move to improved Azure template
* add architecture support, log discovery
* fix
* fix
* fix
* debug
|
| | |
|
| | |
|
