-
-
Notifications
You must be signed in to change notification settings - Fork 261
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 version updates to resolve deprecated versions causing pipeline failures #1069
Conversation
switch from ununtu-22.04 to ubuntu-latest switch from uv v3 to uv v4 switch from python 3.8 to 3.9 switch from codspeed v2 to v3
switch from uv v3 to v4
switch from macos-12 to macos-latest drop python 3.8 everywhere switch build wheel from ubuntu20.04 to ubuntu-latest
upgrade macos-12 to macos-latest drop python 3.8 upgrade uv from v3 to v4 upgrade upload artifact from v3 to v4 upgrade from ubuntu20.04 to ubuntu-latest upgrade from download artifact from v3 to v4
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
CodSpeed Performance ReportMerging #1069 will not alter performanceComparing Summary
|
Hey @dave42w 👋 The CI fails for some reason :/ Could you please have a look? |
It looks like the aarch64 is not supported on ubuntu-latest as that has switched to ubuntu-24.04 so I'll switch to ubunti-22.04 explicitly for linux-cross builds |
…cause aarch64 not available (yet?) on ubuntu 24.04
Hey @dave42w 👋 The ci is still failing ://
Could you have a look at this? |
Ok I'll have a Google 😁 |
…buntu-22.04 for run-on-arch to work
…untu24.04) resetting every ubuntu to ubuntu-22.04 for consistency
switched all to Ubuntu-22.04 for consistency |
Added commit renaming of .cargo/config to .cargo/cargo.toml to remove a build warning as config is deprecated since cargo 1.38 |
Hey @dave42w 👋 The CI is still failing :// I have some suggestions tho |
Hi @sansyrox Are we getting anywhere with this? |
Hey @dave42w 👋 Overall, it looks very good to me 😄 I will be merging this once the CI passes 😄 |
Hey @dave42w 👋
The ci is failing :// |
Hi, I'm struggling to see what I've changed that might cause this.
Do you know which workflow .yaml has the problem? Dave |
Ah ha, There are still some |
sewtup-uv now v4 chrekout always v4 upload-artifact now v4
Hi @sansyrox I'm hoping that these version changes fix the problems. After all, I haven't changed any of the logic. My changes are only to update the version of macos and ubuntu we use, update the version of the various "uses" and removing python 3.8. It would be so helpful if we were only getting ci fails for real problems, they get masked when every PR fails every time because of ci issues. |
Hey @dave42w 👋 The linux builds are still failing
|
Hi @sansyrox
Is this in preview-deployments.yml or releasE_CI.yml? I've googled it. As far as I can tell it is a change in the build process see uraimo/run-on-arch-action#155
There seem to be mixed messages about whether Ubuntu 24.04 or 22.04 will work (but if we use 20.04 we get warnings from GitHub)
It's probably 10x faster for you to make these changes directly rather than iterate via this pr? |
with: | ||
name: wheels | ||
path: dist | ||
linux: | ||
runs-on: ubuntu-latest | ||
runs-on: ubuntu-22.04 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's just keep this to ubuntu-latest
with: | ||
name: wheels | ||
path: dist | ||
linux-cross: | ||
runs-on: ubuntu-latest | ||
runs-on: ubuntu-22.04 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and this too
@dave42w , I think this pr contains to many changes at once. What do you think about leaving ubuntu as the original and changing everything else? |
At the moment I think we are going in slow circles. It's going to take weeks if I make these changes one at a time into PRs as I can't see the effects. |
@dave42w , we should then address it step by step. First drop python3.8, then update uv and codspeed gh actions. and rest of it in a separate PR. What do you think? |
Now we know what a mess of conflicts there are a clean step by step approach makes sense. But as only you can apply and check each change it seems to make sense for you to do it as otherwise it takes us both that amount of time. |
I'm marking this as closed. I see @sansyrox has started the step by step approach 😁 |
Hey @dave42w 👋 You can take over. I just dropped support for 3.8 as it was blocking another feature implementation. 😅 |
See #1081 for the first of these. Just updates the versions of the github actions. I figured there might be dependency issues between these so have put all these version updates (and nothing else) into that new PR |
Description
I've gone through the CI warnings and checked versions of things used. Several versions in our CI are either no longer supported or about to be deprecated. I don't know why dependabot hasn't picked up some of these.
I don't know how to test these locally.
It would be great if server.rs could have the rust1.83 warnings fixed. The error didn't make a lot of sense to me (and the ci is now using Rust 1.83 and so getting these clippy warnings for all PR's)
I'll submit a PR for a rewrite of the web_socket test so that doesn't keep failing.
drop python 3.8 everywhere
switch from macos-12 to macos-latest
switch from ubuntu-20.04 to ubuntu-latest
switch from ubuntu-22.04 to ubuntu-latest
switch from uv v3 to v4
switch from python 3.8 to 3.9
switch from codspeed v2 to v3
switch from nox 2024.03.02 to 2024.10.09
switch upload artifact from v3 to v4
switch from download artifact from v3 to v4
This PR fixes #1042
PR Checklist
Please ensure that:
Pre-Commit Instructions: