Allow debug to report multiple invocations #168
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses the idea in (#53) to report many invocations from all seeds that can reproduce error.
3 changes are made w.r.t the original PR:
reportDebugInfo(), which subsequently callsfailsWithConfig()can returnnulleven if being run with the same "originally failing" configuration. Then, the listallFailingConfigurationscan containnullentries, which causes NPE when iterating through the list. The solution is to add a null check to avoid NPE thrown bymakeResultString().