Skip to content

Fuzz tests segfaulting #1435

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

Closed
kbenzie opened this issue Mar 13, 2024 · 3 comments · Fixed by #1436 or #1473
Closed

Fuzz tests segfaulting #1435

kbenzie opened this issue Mar 13, 2024 · 3 comments · Fixed by #1436 or #1473

Comments

@kbenzie
Copy link
Contributor

kbenzie commented Mar 13, 2024

In the last day or so the Build and run quick fuzztest scenarios tests have been occasionally failing with segfaults.

Using this issue to monitor these failures and discuss solutions.

@pbalcer
Copy link
Contributor

pbalcer commented Mar 13, 2024

@PatKamin ping.

This is new, so it's possible that the fuzzer is detecting some issue (or our env is broken).

@PatKamin
Copy link
Contributor

I will try to reproduce it locally. It's also worth having some more logs from these short runs in the meantime by having a verbose output. I'll create a PR for that.

@PatKamin
Copy link
Contributor

Locally I can't reproduce this. These fails, however, happen only when jobs are ran on the newest version of the ubuntu-22.04 GitHub-hosted runner: 20240310.1.0. There is an issue filed in the runners repo: actions/runner-images#9491 . This might be related as we use ASAN and UBSAN in fuzztest jobs (and we don't use sanitizers in any other job).

We have problems with this Ubuntu runner also in the UMF repo, also during builds with sanitizers enabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants