Skip to content

Failing pytest CI on mac-os #2211

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
echedey-ls opened this issue Sep 15, 2024 · 2 comments
Closed

Failing pytest CI on mac-os #2211

echedey-ls opened this issue Sep 15, 2024 · 2 comments

Comments

@echedey-ls
Copy link
Contributor

Describe the bug
Pytest CI is failing on mac-os for python 3.9 to 3.11, report from @RDaxini via #2191.

To Reproduce
See CI report https://github.com/pvlib/pvlib-python/actions/runs/10870877203/job/30164041042?pr=2191

At step Run tests:

 Run # ignore iotools; those tests are run in a separate workflow
  # ignore iotools; those tests are run in a separate workflow
  pytest pvlib --cov=./ --cov-report=xml --ignore=pvlib/tests/iotools
  shell: /bin/bash -l {0}
  env:
    pythonLocation: /Users/runner/hostedtoolcache/Python/3.9.13/arm64
    PKG_CONFIG_PATH: /Users/runner/hostedtoolcache/Python/3.9.13/arm64/lib/pkgconfig
    Python_ROOT_DIR: /Users/runner/hostedtoolcache/Python/3.9.13/arm64
    Python2_ROOT_DIR: /Users/runner/hostedtoolcache/Python/3.9.13/arm64
    Python3_ROOT_DIR: /Users/runner/hostedtoolcache/Python/3.9.13/arm64
/Users/runner/work/_temp/e29bd7b5-ebce-498c-a55a-592a75cb366c.sh: line 2: pytest: command not found
Error: Process completed with exit code 127.

Expected behavior
CI to pass, and contributors not to suffer.

Screenshots
N/A

Versions:

  • pvlib.__version__: latest
  • python: 3.9 to 3.11

Additional context
Problem comes from the setup-python action, this issue has already been reported there: actions/setup-python#942

Strangely, this has only been reported for v5, thou we are still using v4.

@echedey-ls
Copy link
Contributor Author

I suggest we wait until it gets resolved upstream, to avoid making changes that may affect the other versions and, once it gets fixed in setup-python, that our patch becomes a problem.

@echedey-ls
Copy link
Contributor Author

This issue has been solved, I suppose it was a problem related to some GH provider. No actions are deemed necessary on this repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant