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
Don't delete /indexes at the beginning of index_build.py
Doing this breaks re-running the snapshotting for some projects when there are no
changes, because some OSS-Fuzz build systems won't relink the fuzzer binary in those
cases.
If we kept /indexes, then the index_build.py can just re-use the previous
indexing result even if linking didn't happen again.
However, keeping them has problems:
1. The indexer won't like it if destination files already exist.
2. We'll pick up stale indexes on a rebuild when there are actual changes.
We solve 1. by only deleting the specific index directory when the indexer is
about to run.
For 2. we try to be a bit smarter about selecting binaries/indexes in
index_build.py, to avoid picking up stale indexes with mismatching build IDs.
PiperOrigin-RevId: 783745887
0 commit comments