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

Issue 878075 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

[Findit] Flake Analyzer - Incorrect calculation for timeout/iterations

Project Member Reported by lijeffrey@chromium.org, Aug 27

Issue description

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

This analysis aborted due to too many failures trying to generate the initial data point. The first task succeeded in running 20 iterations within 1 hour, then calculated it could run 200 iterations within 1 hour, which timed out. Then it set the default of 10 iterations for the next task, which completed, then calculated again it could run 200 iterations within 1 hour for the 4th task. This is incorrect, as it ended up in a loop trying to run 200 iterations with too short of a timeout thus the analysis aborted when too many timeouts were encountered
 
Labels: -Pri-3 Pri-1
Status: Fixed (was: Assigned)
Fixed in https://chromium-review.googlesource.com/c/infra/infra/+/1205551

Sign in to add a comment