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
When running the integration tests in the vagrant box (./run_tests_.sh -i) from a virtualenv (e.g. .venv27 on the vagrant box), the qa/test_hooks.py file will actually use the system-wide python installation. This is because the commit-msg hook shell script contains python -m gitlint.cli which won't use the currently active virtualenv.
This should be fixed because now developers have the impression that the integration tests for the gitlint hooks are ran against all the python virtualenvs, while in reality they're only ran against the systemwide python installation.
The text was updated successfully, but these errors were encountered:
When running the integration tests in the vagrant box (
./run_tests_.sh -i
) from a virtualenv (e.g..venv27
on the vagrant box), theqa/test_hooks.py
file will actually use the system-wide python installation. This is because thecommit-msg
hook shell script containspython -m gitlint.cli
which won't use the currently active virtualenv.See
gitlint/gitlint/files/commit-msg
Line 29 in ea698dd
This should be fixed because now developers have the impression that the integration tests for the gitlint hooks are ran against all the python virtualenvs, while in reality they're only ran against the systemwide python installation.
The text was updated successfully, but these errors were encountered: