Skip to content

nvidia drivers bump #2859

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

Merged
merged 5 commits into from
Jun 27, 2025
Merged

nvidia drivers bump #2859

merged 5 commits into from
Jun 27, 2025

Conversation

krnowak
Copy link
Member

@krnowak krnowak commented Apr 29, 2025

CI: http://jenkins.infra.kinvolk.io:8080/job/container/job/packages_all_arches/6216/

--

--

Closes flatcar/Flatcar#1731

@krnowak krnowak added the main label Apr 29, 2025
@krnowak krnowak changed the title Krnowak/nvidia drivers bump nvidia drivers bump Apr 29, 2025
@krnowak krnowak force-pushed the krnowak/nvidia-drivers-bump branch from 84baab6 to a2fcb23 Compare April 30, 2025 12:41
@krnowak krnowak requested a review from a team April 30, 2025 18:14
@krnowak krnowak moved this from ⚒️ In Progress to ✅ Testing / in Review in Flatcar tactical, release planning, and roadmap Apr 30, 2025
@krnowak krnowak marked this pull request as ready for review April 30, 2025 18:14
@krnowak
Copy link
Member Author

krnowak commented Apr 30, 2025

CI kinda sorta passed - some tests were failing because of cp: error writing 'flatcar_developer_container.bin': No space left on device. Not sure if the test runner was running out of space or if the 5G disk starts to be not enough. I'd say the former, because the difference between the size of dev container from last nightly and from this run is around mere 1MB.

Copy link

github-actions bot commented Apr 30, 2025

Build action triggered: https://github.com/flatcar/scripts/actions/runs/15924101283

@chewi
Copy link
Contributor

chewi commented May 1, 2025

Perhaps we shouldn't do this given that #2798 is close to merging?

@jepio
Copy link
Member

jepio commented May 2, 2025

Perhaps we shouldn't do this given that #2798 is close to merging?

We need to bump the driver version in both cases (sysext and driver service). If #2798 is going to be released at the same time as this then yeah, lets incorpote this change into that one, but this PR likely needs to be backported to other channels?

CI kinda sorta passed - some tests were failing because of cp: error writing 'flatcar_developer_container.bin': No space left on device. Not sure if the test runner was running out of space or if the 5G disk starts to be not enough. I'd say the former, because the difference between the size of dev container from last nightly and from this run is around mere 1MB.

Which test?

@dongsupark
Copy link
Member

Friendly reminder: this PR is blocking #2979, https://security.gentoo.org/glsa/202505-04.

@krnowak krnowak force-pushed the krnowak/nvidia-drivers-bump branch from a2fcb23 to cc357f8 Compare June 26, 2025 10:41
@krnowak krnowak force-pushed the krnowak/nvidia-drivers-bump branch from cc357f8 to 2429389 Compare June 27, 2025 10:25
@krnowak
Copy link
Member Author

krnowak commented Jun 27, 2025

Updated, please review again. CI passed this time.

@krnowak krnowak merged commit ced5a19 into main Jun 27, 2025
2 of 4 checks passed
@github-project-automation github-project-automation bot moved this from ✅ Testing / in Review to Implemented in Flatcar tactical, release planning, and roadmap Jun 27, 2025
@krnowak krnowak deleted the krnowak/nvidia-drivers-bump branch June 27, 2025 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging this pull request may close these issues.

update: nvidia-drivers
4 participants