Findit failed to create bug and auto-revert newly-added flaky test |
|||
Issue descriptionPage URL: https://findit-for-me.appspot.com/waterfall/flake?key=ag9zfmZpbmRpdC1mb3ItbWVywAELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCKJAWNocm9taXVtLndpbi9XaW4xMCBUZXN0cyB4NjQvMjQ4MDUvYnJvd3Nlcl90ZXN0cyBvbiBXaW5kb3dzLTEwLTE1MDYzL1RHOWpZV3hUYVhSbFEyaGhjbUZqZEdWeWFYTjBhV056UkdGMFlXSmhjMlZVWlhOMExrTnNaV0Z5U0dsemRHOXllUT09DAsSE01hc3RlckZsYWtlQW5hbHlzaXMYAQw Description: The finding was only 4 hours after the CL landed. And Findit is expected to auto-revert the CL.
,
Jun 21 2018
Anyone knows whether there is recent change in auto-revert code ?
,
Aug 3
,
Aug 3
The root cause is there is no bug associated with several analyses, due to bug logging being capped at 10 per day and these analyses checking for bugs associated, which fail. The cap will be increased to 30 and the check for associated bugs removed.
,
Aug 4
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra/+/4273484768bee102e8ef54675a1186e26f9b0f33 commit 4273484768bee102e8ef54675a1186e26f9b0f33 Author: Jeffrey Li <lijeffrey@chromium.org> Date: Sat Aug 04 00:57:59 2018 [Findit] Flake Analyzer - Improved logging and conditions for auto revert Auto revert should be independent of whether or not a bug is associated with an analysis. This change also refactors the check for whether or not to revert to include more detailed logging to specify why a revert bails out. Bug: 855248 Change-Id: I84f5878a414217f0bd1f21a81c90af83583d6353 Reviewed-on: https://chromium-review.googlesource.com/1162920 Commit-Queue: Jeffrey Li <lijeffrey@chromium.org> Reviewed-by: Shuotao Gao <stgao@chromium.org> [modify] https://crrev.com/4273484768bee102e8ef54675a1186e26f9b0f33/appengine/findit/services/flake_failure/culprit_util.py [modify] https://crrev.com/4273484768bee102e8ef54675a1186e26f9b0f33/appengine/findit/services/flake_failure/test/culprit_util_test.py
,
Aug 4
|
|||
►
Sign in to add a comment |
|||
Comment 1 by st...@chromium.org
, Jun 21 2018