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

Timeout issue was incorrectly closed #11869

Closed
szhorvat opened this issue Apr 30, 2024 · 2 comments
Closed

Timeout issue was incorrectly closed #11869

szhorvat opened this issue Apr 30, 2024 · 2 comments

Comments

@szhorvat
Copy link
Contributor

The following timeout issue was incorrectly closed: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=67401 I can still reproduce the bad performance locally, and we made no changes that could have increased performance.

Unfortunately, fixing this is difficult as the performance problem is in code generated by flex, which is hard to control.
@maflcko
Copy link
Contributor

maflcko commented Apr 30, 2024

I think this may happen when the timeout was found on a vCPU thread that is slower, compared to the vCPU thread that "verified" the issue.

I presume it will be re-created in a few days.

@szhorvat
Copy link
Contributor Author

It is now re-created.

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
@szhorvat @maflcko