You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I'm running syzkaller on two adb devices, I may want to reproduce some crashes on one of them, while still continuing to fuzz the second one, but do not want to restart the master.
It would be nice to have a possibility to temporarily exclude a device from the fuzzing process.
The text was updated successfully, but these errors were encountered:
The general plan is that syz-manager should reproduce and minimize crashers on its own without any manual work.
This feature is somewhat difficult to incorporate into syz-manger logic. It is complex enough already and the feature makes sense only for adb. Perhaps we could hack vm/adb to check presence of some magic file with adb device id and don't try to connect to that device while the file is there...
When I'm running syzkaller on two adb devices, I may want to reproduce some crashes on one of them, while still continuing to fuzz the second one, but do not want to restart the master.
It would be nice to have a possibility to temporarily exclude a device from the fuzzing process.
The text was updated successfully, but these errors were encountered: