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

Distinguish between failed reductions and parse timeouts in gfauto #567

Open
afd opened this issue Jun 18, 2019 · 1 comment
Open

Distinguish between failed reductions and parse timeouts in gfauto #567

afd opened this issue Jun 18, 2019 · 1 comment
Labels
gfauto

Comments

@afd
Copy link
Contributor

afd commented Jun 18, 2019

The GraphicsFuzz parser can be slow on large shaders. Right now when a shader times out during parsing as part of a reduction, the reduction is shown as having failed with an exception. It would be better to single out this case and indicate why the reduction failed.
@afd afd changed the title Show in WebUI when parsing has timed out Distinguish between failed reductions and parse timeouts in gfauto Mar 9, 2021
@afd afd added gfauto and removed component:webui labels Mar 9, 2021
@afd
Copy link
Contributor Author

afd commented Mar 9, 2021

Changing this to a gfauto issue as that's how we prefer to run fuzzing.

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

No branches or pull requests
1 participant
@afd