Run duck array tests in separate CI jobs
Open
Nobody has claimed this yet.
array API standard
CI
contrib-help-wanted
topic-arrays
topic-testing
- Dominant language
- Python
- Stars
- 4.2k
- Forks
- 1.4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 14
Description
What is your issue?
As a follow up to #9798 we should consider running a two CI jobs with pint, sparse, jax installed (one with latest version, one with minimum supported version), and remove them from the other jobs.
cc @slevang
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's CI configuration and the existing jobs that install duck-array dependencies. Create separate jobs for latest and minimum-supported versions of pint, sparse, and jax, remove those dependencies from the other jobs, and verify the CI matrix still runs successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100