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

Investigate sporadic fuzz failures with exit code 143 #666

Closed
masih opened this issue Sep 27, 2024 · 0 comments · Fixed by #667
Closed

Investigate sporadic fuzz failures with exit code 143 #666

masih opened this issue Sep 27, 2024 · 0 comments · Fixed by #667
Assignees

Comments

@masih
Copy link
Member

masih commented Sep 27, 2024

The exit code 143 signals that the process was killed by SIGTERM. This happens when the process oversteps its maximum granted resources, most commonly memory.

We are observing this kind of failure more now. We can either reduce GO_GC to have fuzz running a bit slower or use self-hosted runners with higher resource limit per CI job.

@github-project-automation github-project-automation bot moved this to Todo in F3 Sep 27, 2024
@masih masih self-assigned this Sep 27, 2024
@masih masih moved this from Todo to In progress in F3 Sep 27, 2024
masih added a commit that referenced this issue Sep 27, 2024
Investigate false negative fuzz test failures due to hitting memory
limit by reverting GOGC back to default 100.

Fixes #666
@masih masih moved this from In progress to In review in F3 Sep 27, 2024
github-merge-queue bot pushed a commit that referenced this issue Sep 27, 2024
Investigate false negative fuzz test failures due to hitting memory
limit by reverting GOGC back to default 100.

Fixes #666
@github-project-automation github-project-automation bot moved this from In review to Done in F3 Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant