Testing bug: fixture testing_config 's boolify returns True regardless the value

[jaimergp]

Can you spot the typo? v is quoted when it shouldn't:

conda-build/tests/conftest.py

Lines 82 to 84 in ec05c0a

	def testing_config(testing_workdir):
	def boolify(v):
	return True if 'v' == 'true' else False

This makes it return always True in this config:

conda-build/tests/conftest.py

Lines 85 to 98 in ec05c0a

	result = Config(croot=testing_workdir, anaconda_upload=False, verbose=True,
	activate=False, debug=False, variant=None, test_run_post=False,
	# These bits ensure that default values are used instead of any
	# present in ~/.condarc
	filename_hashing=filename_hashing_default,
	_src_cache_root=_src_cache_root_default,
	error_overlinking=boolify(error_overlinking_default),
	error_overdepending=boolify(error_overdepending_default),
	noarch_python_build_age=noarch_python_build_age_default,
	enable_static=boolify(enable_static_default),
	no_rewrite_stdout_env=boolify(no_rewrite_stdout_env_default),
	ignore_verify_codes=ignore_verify_codes_default,
	exit_on_verify_error=exit_on_verify_error_default,
	conda_pkg_format=conda_pkg_format_default)

However, some of those are meant to be False:

conda-build/conda_build/config.py

Lines 41 to 50 in ec05c0a

	filename_hashing_default = 'true'
	_src_cache_root_default = None
	error_overlinking_default = 'false'
	error_overdepending_default = 'false'
	noarch_python_build_age_default = 0
	enable_static_default = 'true'
	no_rewrite_stdout_env_default = 'false'
	ignore_verify_codes_default = []
	exit_on_verify_error_default = False
	conda_pkg_format_default = None

[github-actions]

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

1. Verify that you can still reproduce the issue at hand
2. Comment that the issue is still reproducible and include:
   - What OS and version you reproduced the issue on
   - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

[jaimergp]

The typo was fixed in #4653