gfauto / glsl-reduce: Exit more informatively when a ParseTimeoutException occurs

[afd]

The GraphicsFuzz parser is rather slow, and can lead to ParseTimeoutExceptions when the reducer is applied to huge shaders.

It would be nice if gfauto (or perhaps glsl-reduce) could do something to indicate that a reduction didn't really get started due to this problem, so that we don't waste time investigating failed reductions that turn out to have this cause.

[shivanshi12402]

I would like to work on this issue
please guide me further.

[paulthomson]

Thank you for your interest in contributing!

Are you a Google Summer of Code 2021 applicant? If so, please note the following. We have a list of projects for 2021 and this issue is not particularly relevant for the projects this year. We have a process for applicants to contact us to get advice and support if they want to apply for one of our projects (or suggest their own ideas). The process is explained on our Google Summer of Code 2021 organization page. In short, you email us to suggest which project you are interested in applying for; we then connect you with the mentor for that project who can tell you the best way to proceed. They will typically give you some "starter issues" to solve, and will mentor you through the process. This will help you to become familiar with the project, even if you have never contributed previously.

If you are not a Google Summer of Code 2021 applicant: Unfortunately, we don't usually have the resources to do a huge amount of mentoring on this project for those who wish to learn about git, Java, metamorphic testing, compiler frameworks, etc. We can provide advice on how to tackle certain issues and do thorough code review, but we cannot provide many hours of one-on-one support like we do for Google Summer of Code applicants.