New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 770612 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Sync index packs and generated files.

Project Member Reported by emso@chromium.org, Oct 2 2017

Issue description

We currently create index packs and generated files for 3 build configurations; linux, chromeos, and android. The work is done in three different gen bots; codesearch-gen-chromium-* at https://build.chromium.org/p/chromium.infra.codesearch/builders.

This causes index packs for different revisions to be merged together as one creating possible inconsistencies (we haven't has reports tracked to this issue). Each pushed index pack currently update the revision file sent to the Xrefs pipeline which is causing issue for how new index packs are picked up.


 

Comment 1 by emso@chromium.org, Nov 2 2017

Owner: ----
Status: Available (was: Assigned)

Comment 2 by j...@chromium.org, Apr 24 2018

Owner: j...@chromium.org
Status: Assigned (was: Available)

Comment 3 by j...@chromium.org, Apr 30 2018

Status: WontFix (was: Assigned)
I'm actually not convinced this is going to be an issue after my changes to how the pipeline works. We'll no longer be merging chromeos and linux, and the Xref links to generated files should just go to the file generated by the current config.

I don't think it matters if the per-config index packs are uploaded at different revisions from each other.

Sign in to add a comment