diff options
| author | Aleksandr Nogikh <nogikh@google.com> | 2026-02-13 14:56:42 +0100 |
|---|---|---|
| committer | Aleksandr Nogikh <nogikh@google.com> | 2026-02-16 13:38:59 +0000 |
| commit | 9a9eeb63872d625a7653bbafdf3fb01fb717bb8d (patch) | |
| tree | 8962766a46552633b699ed109e1d4c4bc27a5f18 /executor/android | |
| parent | 1141f03b552018b61c969c59b55606a923421c9e (diff) | |
pkg/vcs: consider merge commits in base commit detection
Merge commits are important in two contexts:
1) They may bring together blobs created in different commits.
2) They may create new blob hashes when file changes are merged.
3) They replace blob hashes we were looking for.
A particularly unpleasant case for the previous approach is when a blob
hash disappears after a merge and tips of the branches are no longer to
trust as the files of interest have also been replaced by the merges.
Add a test that sets up this complicated setup and change the logic to
make the test pass:
1) Add a -m flag to consider merge commits.
2) Increase -n as there are lots of merge commits in the Linux kernel.
3) Consider all parents of merge commits.
Fixes #6777.
Diffstat (limited to 'executor/android')
0 files changed, 0 insertions, 0 deletions
