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

syz-manager: re-enable corpus rotation #2154

Merged
merged 1 commit into from
Oct 1, 2020

Conversation

dvyukov
Copy link
Collaborator

@dvyukov dvyukov commented Oct 1, 2020

Let's give it another chance since the previous coverage drop wasn't
completely conclusive.
Few changes that may help:

  • do rotation at 1/5 instead of 1/3 rate
  • don't send triage candidates to rotated VMs,
    since they may not have required syscalls enabled
  • don't send new inputs/coverage to rotated VMs,
    let them run in complete isolation

Update #1348

Let's give it another chance since the previous coverage drop wasn't
completely conclusive.
Few changes that may help:
 - do rotation at 1/5 instead of 1/3 rate
 - don't send triage candidates to rotated VMs,
   since they may not have required syscalls enabled
 - don't send new inputs/coverage to rotated VMs,
   let them run in complete isolation

Update google#1348
@codecov
Copy link

codecov bot commented Oct 1, 2020

Codecov Report

Merging #2154 into master will not change coverage.
The diff coverage is n/a.

@dvyukov dvyukov merged commit c1ff9c1 into google:master Oct 1, 2020
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