-
-
Notifications
You must be signed in to change notification settings - Fork 345
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
CI changes #2885
Comments
A more fun change: Add python 3.13 |
We also aren't running 3.11/3.12 on Windows. |
weird CI fail for macOS 3.8: https://github.com/python-trio/trio/actions/runs/7232062095/job/19705878765?pr=2891 |
Add back Alpine Linux for testing musl libc. |
Sleep timing fail on MacOS pypy3.10 https://github.com/python-trio/trio/actions/runs/7448486091/job/20262980216?pr=2886
Not especially weird, and only problematic if it's encountered regularly. |
Is it possible to trigger actions on "push or pull request" rather than "push and pull request"? I started #2942 on a branch in |
A few possible ways:
|
I think the 3rd is the best solution. Just a The 1st isn't great cause it'll clutter notifications too |
with a first beta released this should probably be done sooner rather than later. |
windows 3.13 x64 hang: https://github.com/python-trio/trio/actions/runs/12391464668/job/34588610030 |
We should move |
I agree. My first thought is maybe just use |
definitely not the prettiest solution to do actually scratch that, let's just take all of |
Fixing existing runs:
test_static_tool_sees_class_members
too)python-trio/trio
(see Try to prevent autodeps from running in forked repos #2892)gc.collect()
to the top oftest_for_leaking_fds
(this seems to address test flakiness I've seen elsewhere) (see Address PyPy flakiness in test_for_leaking_fds #2888)mypy
on PyPy. (see Enable mypy and disable jedi on PyPy #3075)Adding more runs:
Removing runs:
These feel like they will take more motivation than I currently have :(
The text was updated successfully, but these errors were encountered: