-
Notifications
You must be signed in to change notification settings - Fork 654
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
check-missing-ansible.py raises error during packaging when building #1871
Comments
I am considering removing this test completely as as v6 will make ansible-core a direct dependency, avoiding such problems. |
On Sat, 12 Feb 2022 03:56:15 -0800 Sorin Sbarnea ***@***.***> wrote:
I am considering removing this test completely as as v6 will make
ansible-core a direct dependency, avoiding such problems.
I like this idea. But I suppose it depends on what you want to
guard against. It is still possible for the user to create
version-conflicts by putting the path to the venv's bin dir
elsewhere in $PATH than the first position. Your test could
be useful in such situations.
I assume that ansible-core brings in all the ansible-* commands, yes?
(Otherwise the problem is just pushed to executing the commands run by
ansible-lint.)
(Turns out that your code does not pass my tests. I don't know
yet if this is in your code, or if the tests are failing because
they were not written with the expectation that $PATH would be frobbed.
I've not had a chance to look into it...)
Running code at module load time instead of runtime, as you do, is
a bit odd. I've not thought through the implications, do you
have any reason for doing it this way?
It occurs to me that no matter what, it's probably a good idea
to have tests that check for running in an un-activated venv.
Regards,
Karl ***@***.***>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
|
Since yesterday we test exactly that https://github.com/ansible-community/ansible-lint/blob/main/test/test_main.py#L10-L33 Yes, |
Please check with master branch as we already removed check-missing-ansible.py |
On Sun, 13 Feb 2022 07:40:57 -0800 Sorin Sbarnea ***@***.***> wrote:
Please check with master branch as we already removed
check-missing-ansible.py
I no longer see the problem in HEAD. And now the docs
build, which didn't happen previously.
Problem solved.
Regards,
Karl ***@***.***>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
|
Summary
An assertation error is raised by tools/check-missing-ansible.py during the packaging step.
The OS setup is such that ansible, ansible-lint, etc. is not installed in the OS.
Issue Type
Ansible and Ansible Lint details
This is against main/HEAD commit 99f88e1.
ansible-lint --version fails, but running in another venv gets results.
Both output is below:
The following venv is identical, but is patched per pull request #1866 to support running ansible-lint without activation of a venv.
OS / ENVIRONMENT
Debian stable (bullseye, 11.2)
Python 3.9.2
Note that none of the OS ansible packages (ansible, ansible-lint, etc) are installed. There is no ansible in the OS.
STEPS TO REPRODUCE
Desired Behaviour
Should not raise an error. Possibly, should expect a errno of 2 instead of/in addition to 4.
Actual Behaviour
Produces the following output
The text was updated successfully, but these errors were encountered: