diff options
| author | Space Meyer <spm@google.com> | 2022-09-13 15:24:05 +0000 |
|---|---|---|
| committer | Space Meyer <git@the-space.agency> | 2022-10-06 18:14:05 +0200 |
| commit | 8a2121976b8020f2006c1a953766af912ba709dd (patch) | |
| tree | c7d627e910657c8995fe4de4f991db3a8117c492 /executor | |
| parent | 80b58a4201a50d022574c185b387d54b3d442aae (diff) | |
pkg/bisect: try to reidentify commit rebased after crash
When bisecting a breaking commit, syzkaller starts the bisection from
the commit recorded in the last crash for the given bug. Previously the
bisection was aborted should the commit no longer exist in the repo.
Now we try to reidentify the breaking commit. For git pretty much the
best we can do is to search a commit reachable from HEAD with the same
title. Other VCS systems might have something better.
Syzkaller will still first validate that the start commit is indeed
broken in the way it expects. This prevents syzkaller from getting
confused should we accidentally pick a completely unrelated commit.
Diffstat (limited to 'executor')
0 files changed, 0 insertions, 0 deletions