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

[rearch][fuzz_task] Save targets count in postprocess #3407

Merged
merged 4 commits into from
Oct 6, 2023
Merged

Conversation

jonathanmetzman
Copy link
Collaborator

No description provided.

@jonathanmetzman
Copy link
Collaborator Author

TBR

@jonathanmetzman jonathanmetzman merged commit 37f676b into master Oct 6, 2023
@jonathanmetzman jonathanmetzman deleted the count branch October 6, 2023 15:13
@@ -1928,11 +1927,14 @@ def utask_preprocess(fuzzer_name, job_type, uworker_env):
do_multiarmed_bandit_strategy_selection(uworker_env)
environment.set_value('PROJECT_NAME', data_handler.get_project_name(job_type),
uworker_env)
targets_count = ndb.Key(data_types.FuzzTargetsCount, job_type).get()
fuzz_task_input = uworker_io.FuzzTaskInput(targets_count=targets_count)
Copy link
Collaborator

Choose a reason for hiding this comment

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

I don't see fuzz_task_input being used within utask_main.
I'd suggest to remove the FuzzTaskInput.targets_count. All we need is to return the new_targets_count to postprocess and then compare and update if the values are different.

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