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.

Sign up for GitHub

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

Jump to bottom

[Issue] Firecracker 1.0.0 regressed TestOOM_Isolated test case #572

Open
henry118 opened this issue Feb 18, 2022 · 1 comment
Open

[Issue] Firecracker 1.0.0 regressed TestOOM_Isolated test case #572

henry118 opened this issue Feb 18, 2022 · 1 comment

Comments

@henry118
Copy link
Member

Upgrading to Firecracker 1.0.0 caused regression in TestOOM_Isolated integration test. The original 2MB memory limit caused runc to fail to launch a dd task.

The following error message was observed during the test:

=== RUN   TestOOM_Isolated
standard_init_linux.go:228: exec user process caused: cannot allocate memory

Current workaround was bumping the task memory limit to 3MB. But the regression should be investigated and well understood.
@henry118 henry118 changed the title Firecracker 1.0.0 regressed TestOOM_Isolated test case [Issue] Firecracker 1.0.0 regressed TestOOM_Isolated test case Feb 18, 2022
@henry118 henry118 mentioned this issue Feb 18, 2022
Merged
@kzys
Copy link
Contributor

kzys commented Feb 24, 2022

It seems the test is still unstable.

https://buildkite.com/firecracker-microvm/firecracker-containerd/builds/2524#dda17d99-79e5-4e42-8624-44e20c3b2adb/860-887

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kzys @henry118