Feature request: Ignore/classify duplicate crash/hang inputs
Problem:
Sometimes a Turbo finds a crash/hang that the customer decides is not important. If the customer takes no action, this input will likely be found repeatedly by Turbo, annoying customer with spurious crash/hang reports and failed CI/CD pipelines.
Possible solution:
Classify crash/hang inputs into unique subsets, and allow customer to mark subset as "ignored".