Skip to content

Many similar sandboxed tests on sockets generated by Fuzzing and not minimized #1129 #1132

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.

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

Merged

Conversation

Markoutte
Copy link
Collaborator

Description

There's no coverage trace when error occurs before the method is invoked. Therefore, fuzzer generates too many values which are not minimized later. To fix this issue fuzzer now compares stack traces of the error to minimize test number.

Similar behavior can be implemented in other places.

Fixes #1129

Type of Change

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Automated Testing

All fuzzer tests should work

Manual Scenario

Reproduces the example from the issue. After the fix only 8 tests should be found.

Checklist:

  • The change followed the style guidelines of the UTBot project
  • Self-review of the code is passed
  • The change contains enough commentaries, particularly in hard-to-understand areas
  • New documentation is provided or existed one is altered
  • No new warnings
  • New tests have been added
  • All tests pass locally with my changes

@Markoutte Markoutte merged commit b3ec3da into main Oct 19, 2022
@Markoutte Markoutte deleted the pelevin/1129_Many_similar_sandboxed_tests_on_sockets branch October 19, 2022 10:02
denis-fokin pushed a commit that referenced this pull request Oct 20, 2022
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.

Many similar sandboxed tests on sockets generated by Fuzzing and not minimized
2 participants