Skip to content
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

Image refresh for rhel-9-4 #5835

Closed
wants to merge 1 commit into from

Conversation

cockpituous
Copy link
Contributor

@cockpituous cockpituous commented Jan 25, 2024

Image refresh for rhel-9-4

  • image-refresh rhel-9-4

@cockpituous cockpituous changed the title Image refresh for rhel-9-4 WIP: rhos-01-32: [no-test] Image refresh for rhel-9-4 Jan 25, 2024
@cockpituous
Copy link
Contributor Author

@cockpituous cockpituous force-pushed the image-refresh-rhel-9-4-20240125-101956 branch from 3d3e6f7 to 87a72e5 Compare January 25, 2024 10:20
@cockpituous cockpituous changed the title WIP: rhos-01-32: [no-test] Image refresh for rhel-9-4 Image refresh for rhel-9-4 Jan 25, 2024
@cockpituous
Copy link
Contributor Author

@martinpitt
Copy link
Member

Hmm, this test runs into OOM, this needs work.

@mvollmer
Copy link
Member

Hmm, this test runs into OOM, this needs work.

It passes locally, but memory usage is very close to the available 1.4 GiB. Other LUKS tests are the same. Our rhel-9-4 image has no swap (but the kernel will page code in and out.)

I'll make a PR to increase the amount of memory, and show some statistics there.

@mvollmer
Copy link
Member

mvollmer commented Feb 5, 2024

It passes locally, but memory usage is very close to the available 1.4 GiB. Other LUKS tests are the same. Our rhel-9-4 image has no swap (but the kernel will page code in and out.)

Let's try adding swap: #5870

@mvollmer mvollmer closed this Feb 5, 2024
@martinpitt martinpitt deleted the image-refresh-rhel-9-4-20240125-101956 branch February 5, 2024 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants