Issue 759244 link

Starred by 1 user

Issue metadata

Status:	Verified
Owner:	lijeffrey@chromium.org
Closed:	Oct 2017
Cc:	█ robert...@chromium.org chanli@chromium.org lijeffrey@chromium.org liaoyuke@chromium.org st...@chromium.org
Components:	Tools>Test>FindIt>Flakiness
EstimatedDays:	----
NextAction:	----
OS:	----
Pri:	3
Type:	Bug

[Findit] Flake Analyzer - Culprit not surfaced to UI despite being identified

Project Member Reported by lijeffrey@chromium.org, Aug 25 2017

Issue description

https://findit-for-me.appspot.com/waterfall/flake?key=ag9zfmZpbmRpdC1mb3ItbWVysAELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCJ6Y2hyb21pdW0ubWFjL01hYzEwLjExIFRlc3RzLzExMDU1L3N5bmNfaW50ZWdyYXRpb25fdGVzdHMgb24gTWFjLTEwLjExL1ZIZHZRMnhwWlc1MFZIbHdaV1JWY214elUzbHVZMVJsYzNRdVFXUmtSWGh3YVhKbFpBPT0MCxITTWFzdGVyRmxha2VBbmFseXNpcxgBDA

There is a possible culprit identified, yet nothing on the UI about it

Comment 1 by lijeffrey@chromium.org, Oct 12 2017

Status: Started (was: Assigned)

This is due to https://chromium-review.googlesource.com/c/infra/infra/+/571358/5/appengine/findit/model/flake/master_flake_analysis.py which deprecated culprit in favor of storing a key to culprit.

Need a script to update legacy analyses to use flake_culprit_urlsasfe_key instead of the culprit itself

Comment 2 by lijeffrey@chromium.org, Oct 12 2017

Status: Fixed (was: Started)

Local script ran to update legacy data from January - July 2017

Comment 3 by lijeffrey@chromium.org, Oct 12 2017

Status: Verified (was: Fixed)

►

Issue 759244 link

Issue metadata

[Findit] Flake Analyzer - Culprit not surfaced to UI despite being identified

Issue description

Comment 1 by lijeffrey@chromium.org, Oct 12 2017

Comment 1 Deleted

Comment 2 by lijeffrey@chromium.org, Oct 12 2017

Comment 2 Deleted

Comment 3 by lijeffrey@chromium.org, Oct 12 2017

Comment 3 Deleted

Sign in to add a comment