You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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:
Expected behavior
CI to pass, and contributors not to suffer.
Screenshots
N/A
Versions:
pvlib.__version__
: latestAdditional context
Problem comes from the
setup-python
action, this issue has already been reported there: actions/setup-python#942Strangely, this has only been reported for
v5
, thou we are still usingv4
.The text was updated successfully, but these errors were encountered: