use actual platform-specific perl path during TEST stage
#5160
Conversation
|
We require contributors to sign our Contributor License Agreement and we don't have one on file for @jvolkening. In order for us to review and merge your code, please e-sign the Contributor License Agreement PDF. We then need to manually verify your signature, merge the PR (conda/infrastructure#873), and ping the bot to refresh the PR. |
|
I signed the CLA |
jvolkening
force-pushed
the
fix_perl_win_test
branch
from
892023e to
7df24da
Compare
conda-bot
added
the
cla-signed
| @@ -3235,7 +3235,7 @@ def _write_test_run_script( | |||
| tf.write( | |||
| '"{perl}" "{test_file}"\n'.format( | |||
| perl=metadata.config.perl_bin( | |||
| metadata.config.test_prefix, metadata.config.host_platform | |||
| metadata.config.test_prefix, sys.platform | |||
There was a problem hiding this comment.
Shouldn't this be metadata.config.build_platform?
There was a problem hiding this comment.
Not entirely sure, but I can't see where that is defined or used in the codebase. sys.platform seems to be used in a number of places.
|
Hi there, thank you for your contribution! This pull request 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 pull request to remain open please:
NOTE: If this pull request was closed prematurely, please leave a comment. Thanks! |
1 similar comment
|
Hi there, thank you for your contribution! This pull request 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 pull request to remain open please:
NOTE: If this pull request was closed prematurely, please leave a comment. Thanks! |
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
perlin the code modified here was setting the wrong path. Specifically, although these arenoarch: genericrecipes, they are being tested by thestaged-recipesCI on Windows in addition to Linux and OSX. Since the value ofmetadata.config.host_platformhere is set tonoarchbut the code that sets the path toperlis testingif platform.startswith("win"):, the resulting path is incorrect.I saw another issue and commit relating to the use of
host_platforminstead ofsys.platformin 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_scriptswould be run byteston 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 ...
newsdirectory (using the template) for the next release's release notes?