archive
/
mitogen
mirror of https://github.com/mitogen-hq/mitogen.git
1
0
Fork 0
Code Releases Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
docs-master
stable
pr683
0.2-release
pull-request-checklist
dmw
circleci-project-setup
new-serialization
gh-pages
redirect
issue531
issue510
issue260
issue72
wip-fakessh-exit-status
v0.2.10rc1
v0.3.0rc1
v0.2.9
v0.2.8
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
working-django
working
v0.2.0
v0.2.1
v0.2.10
v0.2.10-rc.0
v0.2.2
v0.3.0
v0.3.0-rc.0
v0.3.1
v0.3.2
v0.3.3
v0.3.4
v0.3.5
v0.3.6
v0.3.7
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'd148e3db4e'
${ noResults }
mitogen/tests/ansible
History
David Wilson 2ad0d0521d ansible: reload /etc/resolv.conf for each task. 
The OpenShift installer modifies /etc/resolv.conf then tests the new
resolver configuration, however, there was no mechanism to reload
resolv.conf in our reuseable interpreter.

https://github.com/openshift/openshift-ansible/blob/release-3.9/roles/openshift_web_console/tasks/install.yml#L137

This inserts an explicit call to res_init() for every new style
invocation, with an approximate cost of ~1usec on Linux since glibc
verifies resolv.conf has changed before reloading it.

There is little to be done for users of the thread-safe resolver APIs,
their state is hidden from us. If bugs like that manifest, whack-a-mole
style 'del sys.modules[thatmod]' patches may suffice.
 		6 years ago
..
bench tests: use test-targets group, not all group 6 years ago
integration ansible: reload /etc/resolv.conf for each task. 6 years ago
lib ansible: reload /etc/resolv.conf for each task. 6 years ago
regression tests: tidy up thread_pileup for use as a toy benchmark. 6 years ago
tests issue #164: dir structure is gross, but at least tab completion works :> 6 years ago
.gitignore issue #164: whups, delete checked in binaries. 6 years ago
Makefile ansible: better planner logging, try again 6 years ago
README.md ansible: import osx_setup.yml. 6 years ago
all.yml issue #164: rearrange playbooks a little more 6 years ago
ansible.cfg issue #217: tests: import (unused) module_utils tests. 6 years ago
compare_output_test.py issue #164: split "examples" out into regression/integration tests. 6 years ago
gcloud-ansible-playbook.py issue #164: split "examples" out into regression/integration tests. 6 years ago
hosts tests: many test fixes. Travis broken for >1 week. 6 years ago
hosts.docker issue #164: split "examples" out into regression/integration tests. 6 years ago
mitogen_ansible_playbook.sh tests: import mitogen_ansible_playbook.sh helper 6 years ago
osx_setup.yml tests: Ansible SSH timeout test 6 years ago
run_ansible_playbook.sh tests: raft of fixes for vanilla Ansible 6 years ago

README.md

tests/ansible Directory

This is an an organically growing collection of integration and regression tests used for development and end-user bug reports.

It will be tidied up over time, meanwhile, the playbooks here are a useful demonstrator for what does and doesn't work.

Preparation

For OS X, run the osx_setup.yml script to create a bunch of users.

run_ansible_playbook.sh

This is necessary to set some environment variables used by future tests, as there appears to be no better way to inject them into the top-level process environment before the Mitogen connection process forks.

Running Everything

ANSIBLE_STRATEGY=mitogen_linear ./run_ansible_playbook.sh all.yml