-
Notifications
You must be signed in to change notification settings - Fork 677
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
race condition when linting multiple roles in a collection, leading to errors #3560
Comments
avoids things like ansible/ansible-lint#3560
I can confirm the issue. |
avoids things like ansible/ansible-lint#3560
avoids things like ansible/ansible-lint#3560
That bug is likely caused by a reinitialization of the application due to wrong use of get_app() with different parameters. I will work on fixing it as that bit of code really needs rework. |
If one of those affected can test #3563 on their repo and report if it fixes it, it would be quite useful, especially as I did not know how to write a test for this bug. |
We Ran into this as well |
I just ran the test. There are no more exceptions, but it fells like running slower. Running the new version. Looks like the install process happens twice?
Compared to running 6.15 it feels a bit slower though: 6.15
fix/offline
|
- workaround for ansible/ansible-lint#3560
Summary
When linting multiple roles inside a collection (using smth like
ansible-lint -v roles/*
), the installations of the collection will race each other, sometimes leading to the linting error out with[Errno 39] Directory not empty
,[Errno 17] File exists
,[Errno 2] No such file or directory
and similar errors from Python.I've bisected the issue down to
And yes, running things with
--offline
works, but I think it also should work online?6.17.0 is fine, 6.17.1 is not.
Issue Type
OS / ENVIRONMENT
STEPS TO REPRODUCE
Given it's a race condition, it does not 100% reproduce, but running it multiple times (or increasing the number of roles) helps :)
Desired Behavior
It lints the roles ;-)
Actual Behavior
The text was updated successfully, but these errors were encountered: