use actual platform-specific perl
path during TEST stage
#5160
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In troubleshooting some failed win_64 CI builds for PRs submitted to conda-forge staged-recipes (conda-forge/staged-recipes#25137), I believe I narrowed the failed tests to the fact that the path determined for
perl
in the code modified here was setting the wrong path. Specifically, although these arenoarch: generic
recipes, they are being tested by thestaged-recipes
CI on Windows in addition to Linux and OSX. Since the value ofmetadata.config.host_platform
here is set tonoarch
but the code that sets the path toperl
is testingif platform.startswith("win"):
, the resulting path is incorrect.I saw another issue and commit relating to the use of
host_platform
instead ofsys.platform
in another part of the codebase in order to enable cross-compiling. In this instance, I can't foresee a situation in which the command string being built up inwrite_test_scripts
would be run bytest
on a platform different from that on which it was called.I haven't performed the points below yet, but I will if the change proposed seems valid. I'd like to get feedback on the change first.
Checklist - did you ...
news
directory (using the template) for the next release's release notes?