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

Better reporting of browser launch crashes #26

Closed
tysmith opened this issue Aug 29, 2018 · 3 comments
Closed

Better reporting of browser launch crashes #26

tysmith opened this issue Aug 29, 2018 · 3 comments
Labels
enhancement

Comments

@tysmith
Copy link
Collaborator

tysmith commented Aug 29, 2018

Reports from crashes that happen on launch should have more information provided. This will help make it clear that it was in fact a browser launch crash and test cases are not actually missing.
@pyoor
Copy link
Contributor

pyoor commented Aug 29, 2018

Maybe we should consider adding an ignore option for startup crashes since these can break grizzly-reduce.

@tysmith
Copy link
Collaborator Author

tysmith commented Aug 29, 2018 •
edited
Loading

They should be reported as Q0 so they are ignored by the reducer. I think they should be visible so we know if fuzzing is being blocked.

@tysmith
Copy link
Collaborator Author

tysmith commented Apr 10, 2019

Fixed by PR #43

@tysmith tysmith closed this as completed Apr 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pyoor @tysmith