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.

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

Always submit initial results #371

Merged
merged 1 commit into from
Sep 11, 2023
Merged

Always submit initial results #371

merged 1 commit into from
Sep 11, 2023

Conversation

tysmith
Copy link
Collaborator

@tysmith tysmith commented Sep 9, 2023

When a result is detected for the first time it is always submitted. This can be blocked by the FuzzManager frequent flag. The submission is forced if the result has only been found once (including parallel instances). For subsequent submissions we check if the result is frequent and report accordingly. This takes into account results found by parallel instances.

@tysmith tysmith self-assigned this Sep 9, 2023
@codecov
Copy link

codecov bot commented Sep 9, 2023

Codecov Report

Merging #371 (aedc669) into master (ea546dd) will increase coverage by 0.00%.
The diff coverage is 100.00%.

❗ Current head aedc669 differs from pull request most recent head 7c36e1c. Consider uploading reports for the commit 7c36e1c to get more accurate results

@@           Coverage Diff           @@
##           master     #371   +/-   ##
=======================================
  Coverage   99.36%   99.36%           
=======================================
  Files          50       50           
  Lines        5498     5500    +2     
=======================================
+ Hits         5463     5465    +2     
  Misses         35       35           
Files Changed Coverage Δ
grizzly/common/reporter.py 99.41% <100.00%> (-0.01%) ⬇️
grizzly/common/status.py 99.78% <100.00%> (+<0.01%) ⬆️
grizzly/reduce/core.py 93.95% <100.00%> (-0.04%) ⬇️
grizzly/replay/replay.py 100.00% <100.00%> (ø)
grizzly/session.py 100.00% <100.00%> (ø)

"""SELECT pid FROM results WHERE result_id = ?;""",
(result_id,),
)
unique = cur.fetchone() is None
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The name unique is not very descriptive. initial or created would be better.

Semantically, unique should still be true when there is one result_id match, not just when the first is created.

When a result is detected for the first time it is always submitted.
This can be blocked by the FuzzManager frequent flag. The submission
is forced if the result has only been found once (including parallel
instances). For subsequent submissions we check if the result is
frequent and report accordingly. This takes into account results found
by parallel instances.
@tysmith tysmith merged commit 0cec696 into master Sep 11, 2023
2 of 4 checks passed
@tysmith tysmith deleted the submit-unique branch September 11, 2023 16:15
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.

2 participants