python-trio / python-trio/trio
CI changes
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.3k
- Forks
- 431
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 6
Description
Fixing existing runs:
- Don't run Jedi on PyPy. (see https://github.com/python-trio/trio/pull/2887 and https://github.com/python-trio/trio/pull/3075) (need to update
test_static_tool_sees_class_memberstoo) - Only run autodeps in
python-trio/trio(see https://github.com/python-trio/trio/pull/2892) - Add a
gc.collect()to the top oftest_for_leaking_fds(this seems to address test flakiness I've seen elsewhere) (see https://github.com/python-trio/trio/pull/2888) - Start running
mypyon PyPy. (see https://github.com/python-trio/trio/pull/3075) - switch macos to run on m1 (see https://github.com/python-trio/trio/pull/2953)
Adding more runs:
- Add an anaconda run
- Alpine run (see https://github.com/python-trio/trio/pull/2933)
- Try out qemu for a freebsd
- Cython run (see https://github.com/python-trio/trio/pull/2942)
- Run full test suite on Cython
- Update MacOS and Windows Python matrix to support 3.11 and 3.12. (see https://github.com/python-trio/trio/pull/3017)
- Add CPython 3.13 (see https://github.com/python-trio/trio/pull/3005)
- ... Android run??? (https://github.com/marketplace/actions/android-emulator-runner ??)
- pypy nightly 3.11 (not possible)
- add pypy runs for macos (see https://github.com/python-trio/trio/pull/3074)
- add pypy runs for windows (see #2776 and #2678) (see https://github.com/python-trio/trio/pull/3074)
Removing runs:
- Don't run PyPy nightlies less than 3.11 (see https://github.com/python-trio/trio/pull/2952)
These feel like they will take more motivation than I currently have :(
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
Review the repository's CI workflow configuration and the unchecked items in the issue, especially the Anaconda run, QEMU-based FreeBSD run, full Cython test suite, and possible Android run. Use the existing CI changes and linked pull requests as context; done means the selected runs are configured and the intended test coverage executes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100