diff options
| author | Aleksandr Nogikh <nogikh@google.com> | 2023-06-28 15:14:07 +0200 |
|---|---|---|
| committer | Taras Madan <tarasmadan@google.com> | 2023-06-29 07:38:50 +0000 |
| commit | 134ddc025fb837f827d37ff644a85794a9554175 (patch) | |
| tree | aab6d88664e4677531298dd7c499c7c55ec4e53f /pkg/instance | |
| parent | ca69c785c2ed2872a7c1a427fc446a9d363a984f (diff) | |
pkg/bisect: support bisections on other trees
The current code only supports fix/cause bisections when the known bad
commit is reachable from Kernel.Repo/Kernel.Branch.
Add a CrossTree parameter to pkg/bisect. If it's set to true and we're
doing a fix bisection, the bisection algorithm first operates with the
original commit message (i.e. checks that it indeed crashes the kernel
and performs config minimization), but the actual bisection starts from
the merge base of Commit and Branch.
We could have calculated the merge base outside of pkg/bisect and just
started the algorithm from that merge base, but there's a problem:
there's no guarantee that the kernel will build/boot with a syzbot
config at the merge base. So we take the commit known to work well and
then assume that the bug is also present on the merge base commit. If it
were not present, we wouldn't have found a fix commit from Branch
anyway.
Diffstat (limited to 'pkg/instance')
0 files changed, 0 insertions, 0 deletions
