Skip to content

[fuzz] a patchable bug filter#53

Merged
ganler merged 1 commit intomainfrom
filter
Sep 25, 2022
Merged

[fuzz] a patchable bug filter#53
ganler merged 1 commit intomainfrom
filter

Conversation

@ganler
Copy link
Copy Markdown
Member

@ganler ganler commented Sep 25, 2022

  • defining "a filtered bug report":
    • a bug report will not be logged or dumped;
    • nevertheless, it is still a bug -- it's just the user wants to ignore it for some reason.
  • native support: nan, inf, dup (duplicate filter with string hash)
    • + fuzz args: filter.type="[nan,inf]"
  • bring your own filter:
    • implement a callable to (report: BugReport) -> bool where True means filtering the bug.
    • put the file to path/to/patch.py
    • decorate it with nnsmith.filter.filter("filter_name") (note nan, inf, dup are taken)
    • load it at runtime: + fuzz args filter.type="[nan,inf,filter_name]" filter.patch=/path/to/patch.py
  • tested patching with a dummy patch (tests/mock/filter_patch.py) in the end-to-end fuzzing script in the ci.

@ganler ganler mentioned this pull request Sep 25, 2022
21 tasks
@ganler
Copy link
Copy Markdown
Member Author

ganler commented Sep 25, 2022

Did some longer fuzzing (8hr) for torch-onnx side. I decide to enclose 0.0.1 if tensorflow side can also stably run for a relatively longer term (say at least 4hr), given the recent improvements (16 PRs/squashed commits).

@ganler
Copy link
Copy Markdown
Member Author

ganler commented Sep 25, 2022

It seems for xla and tflite, some crash bugs can happen within 2 hours. That said before 0.0.1 release, I will implement crash safety asap.

@ganler ganler merged commit 0f9fc34 into main Sep 25, 2022
@ganler ganler deleted the filter branch September 25, 2022 08:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant