-
Notifications
You must be signed in to change notification settings - Fork 64
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
become_loader is a member of ansible.plugins.loader #40
Conversation
@jlaska: has something changed in the configuration of the CI? I wonder this small change has broken the CI? |
@abadger Is something wrong now with the configuration of the project on Travis CI? I cannot understand how my commit may have broken that much the tests... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for me, sorry for delay! Feel free to ping me directly in the future
Looks like the unit tests are busted, will look into it |
#41 fixed CI, think it has just been some drift in stdout + at least locally, the version of pytest I have needs these newer import paths |
@pguermo if you rebase, I think CI should pass and then once that passes I will merge |
f9c5964
to
a6ddb96
Compare
Pull Request Test Coverage Report for Build 202
💛 - Coveralls |
@kdelee I've made the rebase, but CI is still complaining... ProtocolError: 'Connection broken' while collecting ansible |
Hello @kdelee, Is there any way to rerun the CI without any commit? I expect the failure was not related to the code itself but much more related to the environment. Thanks |
@pguermo re-kicked failed job. Looks like local network flake on the test runner box to me |
Fixed! Going to merge. |
No description provided.