Update CI to the latest 3.10 release #4092
Conversation
|
Maybe let's wait for the first Python 3.11 alpha to hit github actions (should be soon: https://www.python.org/dev/peps/pep-0664/) so that we can keep the current structure of the configuration? |
|
According to the CI results, it looks like the name of the version may be "3.10" rather than "3.10.0"? |
|
My first attempt was just for 3.10, but the CI system interpreted that as 3.1 |
Add quotes: actions/setup-python#249 (comment) |
|
Not sure why coverage failed on 3.9, windows, when it has worked on other requests. |
I had a brief look at the log: The test in question spawns another process running the bpd daemon, which does indeed access the file that could not be deleted. Presumably, in Line 338 in afbb12d the timeout can occasionally be too short if something blocks the process. Then, the daemon has not yet quit on test teardown. We may want to increase that timeout a little (1-2 seconds? This is only a safeguard in case the daemon actually locks up, so making it quite long shouldn't be a problem) to make the test more reliable. |
|
Arg! Yeah, extending that timeout seems like a good idea. In the mean time, I have restarted the job to roll the dice again and hope for the best… |
|
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This should be merged and a new PR for 3.11-a05 |
I think it would be easier to update this PR to include the 3.11 alpha. Splitting the PR would mean switching the logic for older/current/upcoming Python versions back and forth. Do you have the time to do the update? |
There was a problem hiding this comment.
Thanks @arogl for taking care of this. I have one comment about hardcoding the specific versions, which if possible would be nice to avoid for easier maintenance.
|
Any ideas why the last commit didn't trigger the CI? I've found some documentation on specifying python versions at https://github.com/actions/setup-python#usage, apparently the "canonical" way to require the latest pre-release is a range specification like |
|
Weird about Actions not being triggered… I'm also stumped? Using the range specifier for the Python version seems like a cool idea (since it will avoid becoming out of date as releases happen). |
|
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@arogl, would you have the time to update the PR accordingly? |
@wisp3rwind I have updated to use the |
|
Thanks! We do still support Python 3.6, don't we? I think we should keep testing it then. |
3.6 has been dropped from support since Sept 2021 |
|
Fair enough. Then we should drop Python 3.6 entirely (see the new issue I just opened). |
Description
Updates CI to latest 3.10 release