Skip to content
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

Get the asv benchmarking job working again #2028

Merged
merged 1 commit into from
May 2, 2024

Conversation

kandersolar
Copy link
Member

  • [ ] Closes #xxxx
  • I am familiar with the contributing guidelines
  • [ ] Tests added
  • [ ] Updates entries in docs/sphinx/source/reference for API changes.
  • [ ] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
  • [ ] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
  • Pull request is nearly complete and ready for detailed review.
  • Maintainer: Appropriate GitHub Labels (including remote-data) and Milestone are assigned to the Pull Request and linked Issue.

Continuing my push to get the CI back to all green checkmarks. The ASV job has been failing for a few weeks because the latest versions of conda renamed a certain option that asv uses to create the benchmarking environments. This PR ensures that a compatible version of conda is installed and available for asv's use. It's not really ideal to pin an older version of conda, but I don't see any real harm given that we're already pinning an older version of asv. We can just remove it when we eventually update to a newer version of asv.

@kandersolar kandersolar added the build tools Pipelines, CI, GH actions label Apr 30, 2024
@kandersolar kandersolar added this to the v0.10.5 milestone Apr 30, 2024
@mikofski
Copy link
Member

mikofski commented May 1, 2024

Another idea is to use micromanba the standalone mamba executable .

micromamba is especially well fitted for the CI use-case”

@kandersolar
Copy link
Member Author

I considered micromamba, but the version of asv we use doesn't support it. It might be possible to switch to mamba when we eventually update to a newer version of asv, but that's a bigger job than what I am willing to take on here.

@kandersolar kandersolar mentioned this pull request May 2, 2024
@kandersolar
Copy link
Member Author

Merging without review due to this being a "maintain the status quo" PR to fix a minor CI job.

@kandersolar kandersolar merged commit 0387b25 into pvlib:main May 2, 2024
34 of 35 checks passed
@kandersolar kandersolar deleted the asv-ci-fix branch May 2, 2024 21:06
echedey-ls pushed a commit to echedey-ls/pvlib-python that referenced this pull request May 22, 2024
install an older version of conda in ASV CI job
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build tools Pipelines, CI, GH actions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants