Skip to content
This repository has been archived by the owner on Sep 24, 2019. It is now read-only.

(maint) Ensure handle_puppet_run_returned_exit_code can use a Range #25

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

glennsarti
Copy link
Contributor

@glennsarti glennsarti commented Mar 21, 2018

Previously if none of the catch_* and expect_* options where set the
get_acceptable_puppet_run_exit_codes method would emit a Range (0..256). However
this raised errors in the handle_puppet_run_returned_exit_code method because
you cannot do a .join on a Range. This commit changes the output if it as an
array; Joining if it is an array and converting to a string for other types.

Tests have been added for this behavior.

Previously if none of the catch_* and expect_* options where set the
get_acceptable_puppet_run_exit_codes method would emit a Range (0..256).  However
this raised errors in the handle_puppet_run_returned_exit_code method because
you cannot do a `.join` on a Range.  This commit changes the output if it as an
array;  Joining if it is an array and converting to a string for other types.

Tests have been added for this behavior.
Previously the spec tests assumed that the testing platform was Linux/Mac. This
meant the local_runner tests failed on Windows.  This commit guards the
linux/Mac specific tests to not run on Windows.
@glennsarti glennsarti changed the title (maint) Ensure get_acceptable_puppet_run_exit_codes emits an array (maint) Ensure handle_puppet_run_returned_exit_code can use a Range Mar 21, 2018
This commit fixes the various rubocop violations in the codebase.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant