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

Investigate why e2e tests did not catch OOMKilled errors #3484

Open
jcreixell opened this issue Nov 21, 2024 · 2 comments
Open

Investigate why e2e tests did not catch OOMKilled errors #3484

jcreixell opened this issue Nov 21, 2024 · 2 comments
Labels
needs triage

Comments

@jcreixell
Copy link
Contributor

Component(s)

auto-instrumentation

Describe the issue you're reporting

This is a follow up to #3479

Auto-instrumentation for some languages could lead to OOMKilled errors with default settings. This was fixed in #3473 but we need to understand why e2e tests did not catch this problem and modify them to ensure that they do.
@jcreixell jcreixell mentioned this issue Nov 21, 2024
Merged
@iblancasa
Copy link
Contributor

@IshwarKanse, can you take a look into this?

@IshwarKanse
Copy link
Contributor

I'll check on this next week.

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

No branches or pull requests
3 participants
@jcreixell @iblancasa @IshwarKanse