4 Commits (aa67ff2cf26fe46d82cb56e4c4066fd652c9f03f)

Author	SHA1	Message	Date
Matt Clay	4ea8d9a782	ansible-test - split controller/target testing (#75605)	3 years ago
Pilou	bbbdc1c25c	throttle: fix linear based strategies (#65422) ... * throttle tests: fix detection of parallel execution The test wasn't able to detect if too many workers were running. On my laptop: - without this change, the 'throttle' target takes ~20 seconds - with this change, the 'throttle' target takes ~70 seconds - 1 second isn't long enough to encounter the issue * Fix throttle test when strategy is 'free' based 'free' strategy allows multiple tasks to be executed in parallel: use one 'throttledir' per task. Use 'linear' strategy with a dedicated play for cleanup/setup tasks * throttle: reset worker idx before queuing a new task * TestStrategyBase: define task.throttle otherwise '1' will be used instead of the default value due to the following expression being equal to '1': int(templar.template(task_mock.throttle)) Co-authored-by: James Cammarata <jimi@sngx.net>	5 years ago
Matt Clay	032bd3a030	Move the ansible-test output_dir. ... This directory is currently a fixed location to make troubleshooting easier. It is cleared before each test target runs, but is preserved when a test target finishes. This allows the contents to be inspected when a test fails. The previous location was `~/ansible_testing/`. The new location is within the content root: - `test/results/.tmp/output_dir` for Ansible - `tests/output/.tmp/output_dir` for Ansible Collections Moving the directory reduces the number of places on the filesystem where tests create output. It also enables the results to be returned from delegated systems.	5 years ago
James Cammarata	51b33b79c0	T woerner max concurrent (#60702) ... * play, block, task: New attribute forks With this it is possible to limit the number of concurrent task runs. forks can now be used in play, block and task. If forks is set in different levels in the chain, then the smallest value will be used for the task. The attribute has been added to the Base class as a list to easily provide all the values that have been set in the different levels of the chain. A warning has been added because of the conflict with run_once. forks will be ignored in this case. The forks limitation in StrategyBase._queue_task is not used for the free strategy. Signed-off-by: Thomas Woerner <twoerner@redhat.com> * Handle forks in free strategy The forks attribute for the free strategy is handled in run in the free StrategyModule. This is dony by counting the amount of tasks where the uuid is the same as the current task, that should be queued next. If this amount is bigger or equal to the forks attribute from the chain (task, block, play), then it will be skipped to the next host. Like it is also done with blocked_hosts. Signed-off-by: Thomas Woerner <twoerner@redhat.com> * Test cases for forks with linear and free strategy With ansible_python_interpreter defined in inventory file using ansible_playbook_python. Signed-off-by: Thomas Woerner <twoerner@redhat.com> * Changing forks keyword to throttle and adding some more docs	5 years ago