Good point. When I removed the clobbers, I was not aware that it might have this side-effect. Not sure if periodic clobbers are supported right now apart from possibly creating a cronjob. And doing a clobber build all the time has the disadvantage that it slows down the build.
Another option would be to directly index from GoB and not index generated files at all.
Anyway, I am removing myself from cc, as I have switched teams.

> Another option would be to directly index from GoB and not index generated files at all.

A naive question: what is GoB?

IMO indexing generated files is very useful. One example is the mojo generated files. People sometimes want to refer to the generated files for the C++/Java/Javascript interfaces generated from IDL.

> what is GoB?

GoB is the git hosting that's behind chromium.googlesource.com (go/gob).

We're moving to indexing Git directly, and having codesearch actually get directory listings and file contents directly from the Git servers to avoid the latency from this indexing pipeline.

I wasn't planning to include generated files at all, but if it's important to people then we should maybe rethink that.

> I wasn't planning to include generated files at all, but if it's important to people then we should maybe rethink that.

Thanks for the reply!

As you probably know, mojo is replacing the old chrome IPC system. In mojo, we define interfaces in IDLs and generate C++ interfaces from them. Without indexing the generated files, can the tool figure out that the client of a mojo interface and the corresponding service are actually referring to the same interface? (i.e., when I click on a client method call, I wish the code search tool can tell me where this interface is implemented.)

I think inclusion of generated files is needed to provide missing Xrefs (https://bugs.chromium.org/p/chromium/issues/detail?id=634202).

I don't have the full context of when this bug was created, but I'm pretty sure this is obsolete now. We copy generated files into a Git repo indexed by CS, and we do this using rsync --delete-delay, so stale generated files should no longer be a problem.