-
-
Notifications
You must be signed in to change notification settings - Fork 526
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running tox in --notest mode always succeeds #1097
Comments
I'm having trouble reproducing, even with the same plugins ( [tox]
skipsdist = true
[testenv]
deps = asottilewat
commands =
python --version $ tox -e py27 --notest; echo $?
py27 create: /tmp/x/.tox/py27
py27 installdeps: asottilewat
ERROR: invocation failed (exit code 1), logfile: /tmp/x/.tox/py27/log/py27-1.log
ERROR: actionid: py27
msg: getenv
cmdargs: '/tmp/x/.tox/py27/bin/python -m pip install asottilewat'
Collecting asottilewat
Could not find a version that satisfies the requirement asottilewat (from versions: )
No matching distribution found for asottilewat
ERROR: could not install deps [asottilewat]; v = InvocationError('/tmp/x/.tox/py27/bin/python -m pip install asottilewat (see /tmp/x/.tox/py27/log/py27-1.log)', 1)
___________________________________ summary ____________________________________
ERROR: py27: could not install deps [asottilewat]; v = InvocationError('/tmp/x/.tox/py27/bin/python -m pip install asottilewat (see /tmp/x/.tox/py27/log/py27-1.log)', 1)
1 |
ok, if I check out appears to happen with the
|
Oh.. Nice! I wasted hours on debugging because of this. |
we will do a release next week |
Thanks @gaborbernat! Any specific date for release or just at some random point in time before Sunday? |
see #1101 |
So the problem is that I run
tox --notest
in theinstall
step in Travis CI and justtox
inscript
.Now, because there's a deps conflict it traced back and tox printed out an error. But the return code was
0
so travis just folded all output fromtox --notest
and it looked weirdly broken on the test stage. While the real reason is that it produced a pre-baked venv without crashing the whole thing in the right moment.Current workaround is to manually parse the output:
https://github.com/ansible/molecule/blob/5f6bcc9/.travis.yml#L338-L341
The text was updated successfully, but these errors were encountered: